CVE-2026-0584
Unknown Unknown - Not Provided
SQL Injection in code-projects Reservation System Enables Remote Attack

Publication date: 2026-01-05

Last updated on: 2026-04-29

Assigner: VulDB

Description
A weakness has been identified in code-projects Online Product Reservation System 1.0. This issue affects some unknown processing of the file app/products/left_cart.php. This manipulation of the argument ID causes sql injection. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-05
Last Modified
2026-04-29
Generated
2026-05-27
AI Q&A
2026-01-05
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
code-projects online_product_reservation_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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.
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.
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 1.0, specifically in the file app/products/left_cart.php. It occurs because the application improperly processes the 'id' parameter by directly including it in SQL queries without proper sanitization or validation. This allows remote attackers to manipulate the SQL commands executed by the system, potentially leading to unauthorized access or modification of the database. [2, 3]


How can this vulnerability impact me? :

The SQL injection vulnerability can allow attackers to remotely execute arbitrary SQL commands on the database. This can lead to unauthorized disclosure of sensitive information, modification or deletion of data, and disruption of the availability of the system. Attackers may extract confidential data, alter shopping cart contents, or compromise the integrity and availability of the application. [2, 3]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by identifying requests to the vulnerable file 'app/products/left_cart.php' with manipulated 'id' parameters that may indicate SQL injection attempts. One method is to monitor HTTP requests for suspicious input patterns in the 'id' parameter. Additionally, attackers can be identified using Google Dorking with the query: inurl:app/products/left_cart.php. Specific commands to detect exploitation attempts could include using tools like curl or wget to test injection points, for example: curl 'http://target/app/products/left_cart.php?id=1' and then trying SQL injection payloads. Network intrusion detection systems (NIDS) can be configured to alert on SQL injection patterns targeting this endpoint. However, no specific detection commands are documented. [2, 3]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include replacing the affected component with an alternative product, as no known countermeasures or mitigations have been documented. Since the vulnerability arises from improper input sanitization of the 'id' parameter in 'left_cart.php', applying input validation and sanitization or using parameterized queries would be ideal, but no official patches or fixes are available. Monitoring for exploitation attempts and restricting access to the vulnerable endpoint can also help reduce risk. [2, 3]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart