CVE-2025-11613
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 /addcategory.php file. It occurs because the cname parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely, potentially manipulating the database in unauthorized ways. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, modification or deletion of data, full system compromise, and potential service disruption. This poses significant risks to 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 /addcategory.php endpoint for SQL injection via the cname POST parameter. A practical approach is to use sqlmap with a crafted multipart/form-data POST request targeting /addcategory.php to confirm the presence of SQL injection. For example, using sqlmap with the URL and POST data containing the cname parameter can reveal the vulnerability by enumerating the database or using time-based blind SQL injection payloads such as those involving SLEEP(5). [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing strict input validation and filtering on the cname parameter to ensure it conforms to expected formats, minimizing database user permissions by avoiding high-privilege accounts for routine operations, and conducting regular security audits to detect and address vulnerabilities promptly. [1]