CVE-2026-2136VulnerabilityPublished 8 Feb 2026Updated 23 Feb 2026

CVE-2026-2136: projectworlds Online Food Ordering System · SQL Injection

Affects projectworlds Online Food Ordering SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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 8 Feb 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
projectworldsOnline Food Ordering System	Affected =1.0	Fixed in–

CPE configurations (1)

cpe:2.3:a:projectworlds:online_food_ordering_system:*:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2026-2136, organizations should implement the following specific measures: 1) Immediately review and update the /view-ticket.php code to use parameterized queries or prepared statements to prevent SQL injection. 2) Apply strict input validation and sanitization on the 'ID' parameter, ensuring only expected numeric or alphanumeric values are accepted. 3) Employ web application firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting this endpoint. 4) Monitor application logs and database access patterns for unusual queries or repeated failed attempts to exploit the vulnerability. 5) If a patch or updated version from projectworlds becomes available, prioritize its deployment in all affected environments. 6) Conduct security code reviews and penetration testing on the entire application to identify and remediate similar injection flaws. 7) Limit database user privileges to the minimum necessary to reduce potential damage from injection attacks. 8) Educate developers on secure coding practices to prevent recurrence of such vulnerabilities. These targeted actions go beyond generic advice by focusing on the specific vulnerable component and practical detection and prevention strategies.

Description

A flaw has been found in projectworlds Online Food Ordering System 1.0. This affects an unknown function of the file /view-ticket.php. Executing a manipulation of the argument ID can lead to sql injection. It is possible to launch the attack remotely. The exploit has been published and may be used.

Impact

The impact of CVE-2026-2136 on organizations using projectworlds Online Food Ordering System 1.0 can be significant. Successful exploitation could allow attackers to access or manipulate sensitive customer data, including order details and potentially payment information if stored insecurely. This compromises data confidentiality and integrity, damaging customer trust and potentially violating data protection regulations. Additionally, attackers might disrupt service availability by altering or deleting database records, affecting business operations. Since the vulnerability can be exploited remotely without authentication, the attack surface is broad, increasing risk especially for publicly accessible systems. Organizations relying on this software for online food ordering may face financial losses, reputational damage, and legal consequences if exploited. The medium severity score indicates that while the vulnerability is serious, it may not lead to full system compromise or widespread disruption without additional factors. However, the presence of published exploit code elevates the urgency for mitigation to prevent potential attacks.

Summary

CVE-2026-2136 is a SQL injection vulnerability identified in version 1.0 of the projectworlds Online Food Ordering System. The issue resides in the /view-ticket.php script, where the 'ID' parameter is improperly sanitized, allowing an attacker to inject malicious SQL code. This injection flaw enables remote attackers to manipulate backend database queries without requiring authentication or user interaction. The vulnerability can lead to unauthorized data access, modification, or deletion, potentially compromising customer order information and other sensitive data stored in the database. The CVSS 4.0 base score is 6.9 (medium), reflecting the ease of exploitation (no privileges or user interaction needed) but limited scope and impact on confidentiality, integrity, and availability. Although no active exploits have been reported in the wild, the availability of exploit code increases the likelihood of attacks. The vulnerability underscores a common web application security issue where input validation and parameterized queries are not properly implemented, exposing the system to injection attacks. Organizations using this software version should urgently assess their exposure and apply appropriate mitigations or patches once available.

References

Community reviews

Loading reviews…