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

CVE-2026-0591: 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-0591, organizations should first verify if they are running version 1.0 of the code-projects Online Product Reservation System. If so, immediate steps include: 1) Implement input validation and sanitization on the id and qty parameters to prevent malicious SQL code injection. 2) Employ parameterized queries or prepared statements in the /app/checkout/update.php script to eliminate direct concatenation of user inputs into SQL commands. 3) Restrict database user permissions to the minimum necessary to limit the impact of potential injection attacks. 4) Monitor web application logs for unusual or suspicious query patterns targeting the vulnerable parameters. 5) If a vendor patch becomes available, apply it promptly. 6) Consider deploying a web application firewall (WAF) with rules to detect and block SQL injection attempts targeting the affected endpoints. 7) Conduct a security code review and penetration testing focused on input handling in the application. 8) Educate developers on secure coding practices to prevent similar vulnerabilities in future releases. These targeted actions go beyond generic advice and address the root cause of the vulnerability.

Description

A vulnerability was identified in code-projects Online Product Reservation System 1.0. The impacted element is an unknown function of the file /app/checkout/update.php of the component Cart Update Handler. Such manipulation of the argument id/qty leads to sql injection. It is possible to launch the attack remotely. The exploit is publicly available and might be used.

Impact

The SQL injection vulnerability in the Online Product Reservation System can have significant impacts on organizations using this software. Successful exploitation can lead to unauthorized access to sensitive customer and transaction data, including reservation details and potentially payment information, undermining confidentiality. Attackers could alter or delete data, affecting data integrity and potentially disrupting business operations. The availability of the system could also be compromised if attackers execute destructive queries or cause database crashes. This can result in financial losses, reputational damage, and regulatory compliance issues, especially for organizations handling personal or payment data. Since the exploit is remotely executable without authentication, the attack surface is broad, increasing the likelihood of compromise. The public availability of exploit code further elevates the risk. Organizations relying on this product for e-commerce or reservation services may face operational disruptions and customer trust erosion if the vulnerability is exploited.

Summary

CVE-2026-0591 identifies a SQL injection vulnerability in the Online Product Reservation System version 1.0 developed by code-projects. The vulnerability resides in the /app/checkout/update.php script, specifically within the Cart Update Handler component. Attackers can manipulate the id and qty parameters, which are insufficiently sanitized, to inject malicious SQL commands. This injection flaw allows remote attackers to execute arbitrary SQL queries on the backend database without requiring authentication or user interaction. The vulnerability can compromise the confidentiality, integrity, and availability of the system's data by enabling unauthorized data retrieval, modification, or deletion. The vulnerability has a CVSS 4.0 base score of 5.3, indicating medium severity. The exploit code is publicly available, increasing the risk of exploitation, although no active exploitation has been reported yet. The vulnerability does not require special privileges or user interaction, making it easier to exploit. The lack of a patch or vendor-provided fix at the time of publication necessitates immediate mitigation efforts by affected organizations. This vulnerability is typical of insecure coding practices where user input is not properly validated or parameterized in SQL queries, highlighting the need for secure development lifecycle practices.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats