CVE-2026-30532
SQL Injection in SourceCodester Online Food Ordering Admin Panel
Publication date: 2026-03-27
Last updated on: 2026-03-30
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| oretnom23 | online_food_ordering_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL Injection vulnerability in the Online Food Ordering System allows attackers to extract sensitive data, including administrator credentials, user information, orders, and products. Such unauthorized access and data exfiltration can lead to violations of data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information.
Because attackers can retrieve and expose sensitive data, this vulnerability undermines the confidentiality and integrity requirements of these standards, potentially resulting in non-compliance, legal penalties, and reputational damage.
Can you explain this vulnerability to me?
CVE-2026-30532 is a SQL Injection vulnerability found in the Online Food Ordering System version 1.0, specifically in the admin/view_product.php file via the "id" parameter.
The vulnerability occurs because the application does not properly sanitize the "id" parameter received through HTTP GET requests, allowing an authenticated attacker to inject arbitrary SQL commands.
The backend database is SQLite, and the injection supports UNION queries as well as boolean-based and time-based blind SQL injection techniques.
This enables attackers to retrieve and display sensitive data such as administrator credentials, user information, orders, and products directly on the webpage.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including:
- Data exfiltration: Attackers can extract entire database contents including users, orders, and products.
- Authentication bypass: Attackers can retrieve administrator credentials to gain unauthorized access.
- System compromise: Attackers can enumerate database schema and server information, potentially leading to further exploitation.
Although the vulnerability requires authenticated access, it poses a high risk due to the ability to execute arbitrary SQL commands and extract sensitive data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL Injection vulnerability can be detected by testing the "id" parameter in the admin/view_product.php page for SQL injection flaws.
A common tool to detect this vulnerability is sqlmap, which can automate the detection and exploitation of SQL injection.
- Use the following sqlmap command to test the vulnerable parameter (replace URL, referer, and cookie values accordingly):
- sqlmap -u "http://127.0.0.1:8088/admin/view_product.php?id=3" --referer="http://127.0.0.1:8088/admin/?page=products" --cookie="PHPSESSID=YOUR_COOKIE_HERE" --batch -v 6 --risk=3
This command targets the id parameter via GET, uses the referer and session cookie to simulate an authenticated admin user, and runs with increased verbosity and risk level to detect the injection.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Restrict access to the admin interface to trusted users only, as the vulnerability requires authenticated access.
- Apply input validation and sanitization on the "id" parameter to prevent SQL injection.
- Use prepared statements or parameterized queries in the admin/view_product.php code to safely handle user input.
- If possible, update or patch the Online Food Ordering System to a version that fixes this vulnerability.
- Monitor logs for suspicious SQL queries or unusual admin activity.
Until a patch is applied, consider disabling or restricting access to the vulnerable admin/view_product.php page.