CVE-2026-30534
SQL Injection in SourceCodester Online Food Ordering Admin Module
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 can this vulnerability impact me? :
This vulnerability can have serious impacts including data exfiltration by retrieving sensitive information directly from the database.
Attackers may bypass authentication by reading administrator credentials stored in the database.
It can lead to system compromise through enumeration of the database schema and server information, potentially allowing unauthorized access or control over the system.
Can you explain this vulnerability to me?
CVE-2026-30534 is a SQL Injection vulnerability found in the Online Food Ordering System version 1.0, specifically in the Category Management component within the file admin/manage_category.php.
The vulnerability occurs because the application does not properly sanitize the 'id' parameter received via HTTP GET requests, allowing an authenticated attacker (such as an administrator) to inject arbitrary SQL commands.
The backend database is SQLite, and the injection point supports UNION queries, enabling attackers to retrieve and display sensitive database information directly on the webpage.
Additionally, blind SQL injection techniques (both Boolean-based and time-based) are possible, which can be used to extract data even when direct output is not available.
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 vulnerable parameter `id` in the URL `admin/manage_category.php` for injection points.
One effective method is to use sqlmap, an automated SQL injection tool, with the following example command to test the injection:
- sqlmap -u "http://127.0.0.1:8088/admin/manage_category.php?id=4" -H "X-Requested-With: XMLHttpRequest" -H "Referer: http://127.0.0.1:8088/admin/?page=maintenance" --cookie="PHPSESSID=YOUR_COOKIE_HERE" --batch -v 6 --risk=3
This command targets the `id` parameter with appropriate headers and session cookie to simulate an authenticated request, allowing detection of UNION-based, Boolean-based, and time-based blind SQL injection.
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 directly from the database, including potentially administrative credentials and confidential information.
Such unauthorized access and data exfiltration can lead to violations of data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized disclosure.
Therefore, exploitation of this vulnerability could result in non-compliance with these standards due to failure to protect sensitive data adequately.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the SQL Injection vulnerability in the Online Food Ordering System v1.0, immediate steps include:
- Restrict access to the vulnerable admin/manage_category.php page to trusted administrators only.
- Avoid using the vulnerable 'id' parameter in HTTP GET requests until a patch or fix is applied.
- Implement input validation and sanitization on the 'id' parameter to prevent injection of arbitrary SQL commands.
- Use prepared statements or parameterized queries in the backend code to handle database queries safely.
- Monitor logs for suspicious activity related to SQL injection attempts targeting the 'id' parameter.
- If possible, temporarily disable the affected functionality until a secure patch or update is available.