CVE-2026-0584VulnerabilityPublished 5 Jan 2026Updated 23 Feb 2026

CVE-2026-0584: code-projects Online Product Reservation System · SQL Injection

Affects code-projects Online Product Reservation SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projectsOnline Product Reservation System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2026-0584, organizations should immediately implement input validation and sanitization on all parameters, especially the 'ID' parameter in app/products/left_cart.php. Employ parameterized queries or prepared statements to prevent SQL injection attacks effectively. If source code modification is not immediately feasible, deploy Web Application Firewalls (WAFs) with custom rules to detect and block malicious SQL injection payloads targeting the vulnerable endpoint. Conduct thorough code reviews and security testing to identify and remediate similar injection points. Monitor database logs and application behavior for unusual queries or access patterns indicative of exploitation attempts. Segregate the database with least privilege access controls to limit the impact of any successful injection. Stay alert for official patches or updates from the vendor and apply them promptly once available. Additionally, consider isolating the affected system from direct internet exposure until mitigations are in place.

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.

Impact

The SQL injection vulnerability can lead to unauthorized access to sensitive data stored in the reservation system's database, including customer information and product reservation details. Attackers could modify or delete data, disrupting business operations and causing data integrity issues. In worst-case scenarios, attackers might escalate their access within the backend database, potentially compromising other connected systems. This could result in financial losses, reputational damage, and regulatory compliance violations for affected organizations. Since the vulnerability is remotely exploitable without authentication, it poses a significant risk to any deployment exposed to the internet. The medium CVSS score reflects moderate impact, but the ease of exploitation and public availability of exploit code increase the urgency for remediation. Organizations relying on this system for e-commerce or reservation management could face service disruption and data breaches if the vulnerability is exploited.

Summary

CVE-2026-0584 identifies a SQL injection vulnerability in the Online Product Reservation System version 1.0 developed by code-projects. The vulnerability resides in the app/products/left_cart.php script, specifically in the processing of the 'ID' parameter. Due to insufficient input sanitization or improper query construction, an attacker can manipulate this parameter to inject arbitrary SQL commands. This injection can be performed remotely without requiring authentication or user interaction, making it accessible to a wide range of attackers. The vulnerability has a CVSS 4.0 base score of 5.3, indicating medium severity, with network attack vector, low complexity, no privileges required, and no user interaction. The impact includes potential unauthorized disclosure, modification, or deletion of database records, which could compromise customer data, transaction records, or system integrity. Although no active exploitation has been reported, the availability of public exploit code increases the likelihood of future attacks. The vulnerability does not require special conditions such as social engineering or elevated privileges, which broadens the attack surface. No official patches have been linked yet, so mitigation relies on secure coding practices and protective controls.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 23:14 UTC

Technical details

References

Community reviews

Related threats