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

CVE-2026-0590: 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-0590, organizations should first seek any official patches or updates from the vendor code-projects and apply them promptly once available. In the absence of patches, immediate remediation includes implementing strict input validation and sanitization on the 'ID' parameter in /app/checkout/delete.php to prevent malicious SQL code injection. Refactoring the code to use parameterized queries or prepared statements is critical to eliminate SQL injection risks. Employing web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting this endpoint can provide temporary protection. Regular security testing, including automated vulnerability scanning and manual code reviews focusing on database query handling, should be conducted. Additionally, monitoring database logs and application logs for suspicious query patterns can help detect exploitation attempts early. Restricting database user permissions to the minimum necessary can limit the damage if exploitation occurs. Finally, educating development teams on secure coding practices will help prevent similar vulnerabilities in future releases.

Description

A vulnerability was determined in code-projects Online Product Reservation System 1.0. The affected element is an unknown function of the file /app/checkout/delete.php of the component POST Parameter Handler. This manipulation of the argument ID causes sql injection. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized.

Impact

The SQL injection vulnerability in the Online Product Reservation System can have significant impacts on organizations that rely on this software for managing product reservations. Exploitation can lead to unauthorized access to sensitive customer data, including personal and transactional information, which compromises confidentiality. Attackers may alter or delete reservation records, impacting data integrity and potentially causing operational disruptions. Availability may also be affected if attackers execute destructive queries or cause database errors, leading to denial of service conditions. The remote and unauthenticated nature of the exploit increases the risk of widespread attacks, especially if the system is internet-facing. Organizations could face reputational damage, regulatory penalties for data breaches, and financial losses due to disrupted business processes. The medium CVSS score reflects moderate risk, but the actual impact depends on the deployment context and the sensitivity of the data managed by the system.

Summary

CVE-2026-0590 identifies a SQL injection vulnerability in the Online Product Reservation System version 1.0 developed by code-projects. The vulnerability resides in the POST parameter handler of the /app/checkout/delete.php script, specifically in the processing of the 'ID' parameter. An attacker can remotely manipulate this parameter to inject arbitrary SQL commands into the backend database query. This occurs because the input is not properly sanitized or parameterized before being incorporated into SQL statements. The vulnerability allows attackers to execute unauthorized SQL queries, potentially leading to unauthorized data retrieval, modification, or deletion. The attack vector is network-based, requiring no authentication or user interaction, which lowers the barrier for exploitation. The CVSS 4.0 vector indicates low complexity (AC:L), no privileges required (PR:L), no user interaction (UI:N), and partial impacts on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). Although no public patches are currently linked, the vulnerability has been publicly disclosed, increasing the risk of exploitation. The system's role in managing product reservations means that exploitation could disrupt business operations and compromise sensitive customer or transactional data.

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