CVE-2026-2136
SQL Injection in Online Food Ordering System /view-ticket.php
Publication date: 2026-02-08
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 |
|---|---|---|
| projectworlds | online_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?
[{'type': 'paragraph', 'content': 'CVE-2026-2136 is a critical SQL injection vulnerability found in version 1.0 of the Online Food Ordering System Project by projectworlds, specifically in the /view-ticket.php file.'}, {'type': 'paragraph', 'content': "The vulnerability occurs because the 'id' parameter from HTTP GET requests is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code."}, {'type': 'paragraph', 'content': 'Exploiting this flaw enables unauthorized access to the database, allowing attackers to view, modify, or delete sensitive data remotely without any authentication.'}] [1, 2, 3]
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': 'This vulnerability can have severe impacts including unauthorized database access, data leakage, data tampering, and potential disruption of system services.'}, {'type': 'list_item', 'content': 'Attackers can view sensitive information stored in the database.'}, {'type': 'list_item', 'content': 'Attackers can modify or delete data, compromising data integrity.'}, {'type': 'list_item', 'content': "The system's availability may be affected due to malicious queries or service disruption."}, {'type': 'list_item', 'content': 'The vulnerability can be exploited remotely without authentication, increasing the risk.'}, {'type': 'paragraph', 'content': 'Overall, this poses a serious threat to system security and business continuity.'}] [1, 2, 3]
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 SQL injection vulnerability can be detected by testing the 'id' parameter in the /view-ticket.php file for SQL injection flaws."}, {'type': 'paragraph', 'content': 'One practical approach is to use the sqlmap tool to automate detection. For example, the following command can be used to test the vulnerability:'}, {'type': 'list_item', 'content': 'sqlmap -u "http://<target-ip>:<port>/view-ticket.php" --data "?id=1 OR 1=1--" --dbs'}, {'type': 'paragraph', 'content': 'Additionally, manual testing can be performed using payloads such as Boolean-based blind SQL injection (e.g., id=-2509 OR 5950=5950 #), time-based blind SQL injection (e.g., id=(CASE WHEN (1797=1797) THEN SLEEP(5) ELSE 1797 END)), or UNION-based SQL injection with multiple columns.'}, {'type': 'paragraph', 'content': 'Vulnerable targets can also be identified by searching for URLs containing "inurl:view-ticket.php" using Google Dorking.'}] [2, 3]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps include:'}, {'type': 'list_item', 'content': 'Implement prepared statements with parameter binding to separate SQL code from user input.'}, {'type': 'list_item', 'content': 'Apply strict input validation and filtering to ensure inputs conform to expected formats.'}, {'type': 'list_item', 'content': "Minimize database user permissions by avoiding the use of high-privilege accounts such as 'root' or 'admin' for application database connections."}, {'type': 'list_item', 'content': 'Conduct regular security audits to detect and fix vulnerabilities promptly.'}, {'type': 'paragraph', 'content': 'If possible, consider replacing the affected software with a secure alternative, as no known countermeasures or patches have been documented.'}] [2, 3]