CVE-2025-11612
BaseFortify
Publication date: 2025-10-11
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| fabian | simple_food_ordering_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-11612 is a SQL injection vulnerability in the Simple Food Ordering System version 1.0, specifically in the /addproduct.php file. It occurs because the application improperly handles the 'category' parameter in HTTP POST requests, directly including it in SQL queries without proper validation or sanitization. This allows attackers to inject malicious SQL code remotely, potentially manipulating the database. [1]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and potential service disruption. Attackers can exploit the flaw to manipulate SQL queries, which threatens the security and business continuity of the affected system. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the `category` parameter in HTTP POST requests to the `/addproduct.php` file for SQL injection. One method is to use time-based blind SQL injection techniques, such as injecting a payload like `SLEEP(5)` to observe delays. The sqlmap tool can be used to automate detection by targeting the `category` parameter in a multipart/form-data POST request. Example sqlmap command: `sqlmap -u http://targetsite/addproduct.php --data="category=1" --method=POST --risk=3 --level=5` and then modify the `category` parameter to test for injection. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implement strict input validation and filtering on the `category` parameter to ensure it conforms to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding high-privilege accounts like `root` or `admin` for routine operations. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. [1]