VulnerabilityPublished 22 Mar 2026Updated 23 Mar 2026

CVE-2026-4533: code-projects Simple Food Ordering System · SQL Injection

Affects code-projects Simple Food Ordering SystemSource CVE Database V5

Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 29 Oct 2026, 19:04 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 23% 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 22 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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-projectsSimple Food Ordering System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2026-4533, organizations should immediately review and update the all-tickets.php file to implement strict input validation and sanitize the 'Status' parameter. The best practice is to replace dynamic SQL queries with parameterized prepared statements or stored procedures to eliminate SQL injection vectors. If source code modification is not immediately feasible, deploying a Web Application Firewall (WAF) with rules to detect and block SQL injection attempts targeting the 'Status' parameter can provide temporary protection. Restricting network access to the vulnerable endpoint to trusted IP addresses and monitoring logs for suspicious query patterns are additional defensive measures. Organizations should also conduct a thorough security audit of the entire application to identify and remediate similar injection flaws. Regular backups of the database are recommended to enable recovery in case of data tampering. Finally, maintain awareness of vendor updates or patches and apply them promptly once available.

Description

CVE-2026-4533 is a medium severity SQL injection vulnerability found in version 1.0 of the code-projects Simple Food Ordering System, specifically in the all-tickets.php file. The vulnerability arises from improper sanitization of the 'Status' parameter, allowing remote attackers to inject malicious SQL commands without authentication or user interaction. Although the exploit code is publicly available, there are no confirmed reports of active exploitation in the wild. Successful exploitation could lead to unauthorized data access or modification within the affected database, impacting confidentiality and integrity. The vulnerability affects a niche food ordering system product, limiting its widespread impact but posing risks to organizations using this software. Mitigation requires immediate input validation and parameterized queries in the affected code, along with monitoring and restricting access to the vulnerable endpoint. Countries with notable usage of this software or similar web applications, including the United States, India, United Kingdom, Canada, Australia, and Germany, may face higher risks. Organizations should prioritize patching or applying workarounds to prevent potential data breaches or service disruptions.

Impact

The primary impact of CVE-2026-4533 is unauthorized access to or manipulation of the backend database of the Simple Food Ordering System. Attackers exploiting this vulnerability could retrieve sensitive customer data, order details, or internal system information, leading to confidentiality breaches. Data integrity could also be compromised if attackers modify or delete records, potentially disrupting business operations or causing financial losses. Availability impact is limited but possible if attackers execute destructive SQL commands. Given the system's role in processing food orders, exploitation could result in operational disruptions for affected businesses. Although the product's market penetration appears limited, organizations relying on this software without mitigation are at risk of data breaches and reputational damage. The public availability of exploit code increases the likelihood of opportunistic attacks, especially against poorly secured deployments. The medium severity rating indicates a moderate but tangible risk that requires timely remediation to prevent exploitation.

Summary

CVE-2026-4533 identifies a SQL injection vulnerability in the Simple Food Ordering System version 1.0 developed by code-projects. The flaw exists in the all-tickets.php file, where the 'Status' parameter is improperly sanitized, enabling attackers to manipulate SQL queries executed by the backend database. This vulnerability can be exploited remotely without requiring authentication or user interaction, increasing its risk profile. The injection allows attackers to execute arbitrary SQL commands, potentially leading to unauthorized data disclosure, data modification, or deletion. The CVSS 4.0 base score is 5.3 (medium), reflecting the ease of exploitation (network attack vector, low attack complexity) but limited impact scope and privileges required (low privileges). No official patches or fixes have been published yet, and while exploit code is publicly available, there are no confirmed active exploits in the wild. The vulnerability primarily threatens organizations using this specific food ordering system, which may be deployed in small to medium-sized restaurants or food service providers. The lack of authentication requirements and remote exploitability make it critical to address promptly. The vulnerability highlights the importance of secure coding practices, especially input validation and use of parameterized queries to prevent SQL injection attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Mar 2026, 20:06 UTC

Technical details

References

Community reviews

Related threats