CVE-2026-4319
SQL Injection in Simple Food Order System’s add-item.php Allows Remote Exploitation
Publication date: 2026-03-17
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 |
|---|---|---|
| carmelo | simple_food_order_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?
[{'type': 'paragraph', 'content': 'CVE-2026-4319 is a critical SQL injection vulnerability found in version 1.0 of the Simple Food Order System, specifically in the file /routers/add-item.php.'}, {'type': 'paragraph', 'content': "The vulnerability occurs because the 'price' parameter in HTTP POST requests is used directly in SQL queries without proper input validation or sanitization."}, {'type': 'paragraph', 'content': 'This allows attackers to inject malicious SQL code remotely, enabling unauthorized manipulation of the database.'}, {'type': 'paragraph', 'content': 'Exploitation does not require any user authentication or authorization, making it highly accessible.'}, {'type': 'paragraph', 'content': 'A proof-of-concept exploit demonstrates a time-based blind SQL injection attack that can delay database responses, confirming the vulnerability.'}] [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, allowing attackers to view, modify, or delete sensitive data.
Attackers may gain comprehensive control over the system, potentially causing service interruptions and compromising data integrity.
Since exploitation requires no authentication, the risk of attack is high and can result in significant operational and security impacts.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This vulnerability can be detected by testing the 'price' parameter in HTTP POST requests to the /routers/add-item.php endpoint for SQL injection. A proof-of-concept (PoC) uses a time-based blind SQL injection payload that causes the database to delay its response, confirming the vulnerability."}, {'type': 'list_item', 'content': 'Use the following payload in a POST request to test for the vulnerability: name=Item6&price=40 AND (SELECT 5454 FROM (SELECT(SLEEP(5)))Asyl)&action='}, {'type': 'list_item', 'content': 'Use sqlmap tool targeting the URL, for example: sqlmap -u "http://<target-ip>/food/routers/add-item.php" --data="name=Item6&price=40&action=" --time-sec=5 --technique=T'}, {'type': 'paragraph', 'content': 'Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:routers/add-item.php'}] [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Use prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection.
- Implement strict input validation and filtering to ensure that inputs conform to expected formats.
- Minimize database user permissions by avoiding the use of high-privilege accounts (e.g., root or admin) for routine operations.
- Conduct regular security audits of code and systems to detect and address vulnerabilities promptly.