CVE-2025-11600
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-11600 is a SQL injection vulnerability in version 1.0 of the Simple Food Ordering System, specifically in the editcategory.php file. The vulnerability occurs because the cname parameter is used directly 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? :
This vulnerability can lead to unauthorized database access, leakage of sensitive data, modification or deletion of data, full system compromise, and potential service disruption. Exploiting this flaw can severely impact 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 `cname` parameter in the `/editcategory.php` file for SQL injection. A proof-of-concept payload uses a time-based blind SQL injection with the MySQL SLEEP() function, for example: `111' AND (SELECT 6545 FROM (SELECT(SLEEP(5)))oUYh) AND 'nYmE'='nYmE`. Sending this payload as a multipart POST request parameter `cname` and observing a delay in server response indicates vulnerability. Additionally, tools like sqlmap can be used to automate detection and extract database information by targeting this parameter. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to separate SQL code from user input, preventing injection; 2) Implementing strict input validation and filtering to ensure inputs conform to expected formats; 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine operations; 4) Conducting regular security audits of code and systems to detect and fix vulnerabilities promptly. These steps help secure the application, protect data integrity, and maintain system availability. [1]