CVE-2025-11603
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?
This vulnerability is a SQL injection flaw in the Simple Food Ordering System version 1.0, specifically in the /editproduct.php file. It occurs because the 'category' parameter is improperly handled and directly used in SQL queries without proper input validation or sanitization. This allows attackers to inject malicious SQL code remotely, potentially manipulating the database unauthorizedly. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, leakage of sensitive data, tampering with or deletion of data, full system control by attackers, and potential service disruptions. This threatens system security and business continuity. [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 the `/editproduct.php` file for SQL injection. A proof-of-concept uses a time-based blind SQL injection payload that injects a `SLEEP(5)` command via a multipart POST request to observe a delay in server response. Additionally, the sqlmap tool can be used to confirm the vulnerability and identify the database system (MySQL 5.0.12 or higher). Example command using sqlmap: `sqlmap -u http://target/editproduct.php --data="category=1" --technique=T --dbms=MySQL` with payloads to test for time delays. [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) Minimize database user permissions by avoiding high-privilege accounts for routine operations. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. [1]