Skip to main content
VulnerabilityPublished Updated

CVE-2026-26711: code-projects Simple Food Order System · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2026-26711, organizations should immediately review and update the /food/view-ticket.php script to implement secure coding practices. Specifically, input validation should be enforced to reject or sanitize all user-supplied data before it is used in SQL queries. The use of prepared statements with parameterized queries is strongly recommended to prevent injection attacks. If possible, upgrade to a patched version of the software once available or apply vendor-provided fixes. In the interim, consider deploying web application firewalls (WAFs) with rules targeting SQL Injection patterns to block malicious requests. Conduct thorough code audits and penetration testing to identify and remediate similar vulnerabilities elsewhere in the application. Additionally, monitor database logs and application behavior for unusual queries or access patterns indicative of exploitation attempts. Restrict database user permissions to the minimum necessary to limit the impact of any successful injection. Finally, educate developers on secure coding standards and the importance of input sanitization to prevent future vulnerabilities.

Description

code-projects Simple Food Order System v1.0 is vulnerable to SQL Injection in /food/view-ticket.php.

References

Community reviews

Loading reviews…