CVE-2026-0590
SQL Injection in code-projects Reservation System POST Handler
Publication date: 2026-01-05
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 |
|---|---|---|
| code-projects | online_product_reservation_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?
This vulnerability is a SQL injection flaw in the code-projects Online Product Reservation System version 1.0. It exists in the POST parameter handler of the file /app/checkout/delete.php, where the ID parameter is improperly handled. Because the application does not validate or sanitize this input, an attacker can manipulate the ID parameter to inject malicious SQL code. This allows the attacker to execute unauthorized SQL commands remotely, potentially compromising the database. [2, 3]
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers to remotely execute arbitrary SQL commands on your database. This can lead to unauthorized access to sensitive data, modification or deletion of data (such as shopping cart contents), and overall compromise of the system's confidentiality, integrity, and availability. Exploitation is possible without authentication, increasing the risk of attack. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring HTTP POST requests to the endpoint /app/checkout/delete.php, specifically looking for suspicious or malformed 'ID' parameter values that may indicate SQL injection attempts. Attackers may use payloads that include SQL syntax in the 'ID' parameter. Additionally, Google dorking with the query 'inurl:app/checkout/delete.php' can help identify vulnerable targets. For detection on your system, you can use tools like curl or wget to send crafted POST requests to test for SQL injection, for example: curl -X POST -d "ID=1' OR '1'='1" http://yourserver/app/checkout/delete.php. Monitoring web server logs for unusual POST requests to this endpoint with suspicious parameter values is also recommended. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing or patching the affected component /app/checkout/delete.php to ensure proper input validation and sanitization of the 'ID' POST parameter to prevent SQL injection. Since no known countermeasures or patches are documented, it is suggested to replace the vulnerable component with an alternative product or apply input sanitization and parameterized queries to the code. Additionally, restricting access to the vulnerable endpoint and monitoring for exploitation attempts can help reduce risk until a permanent fix is applied. [2]