Skip to main content
CVE-2025-6122VulnerabilityPublished

CVE-2025-6122: code-projects Restaurant Order System · SQL Injection

Affects code-projects Restaurant Order SystemSource CVE Database V5

0

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.4% chance of exploitation in 30 days – higher than 37% 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Jun 2025

  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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
code-projects Restaurant Order SystemAffected
  • =1.0
Fixed in–

AI-suggested

1. Immediate mitigation should include restricting external access to the /table.php endpoint by implementing network-level controls such as firewalls or web application firewalls (WAFs) configured to detect and block SQL Injection patterns targeting the 'ID' parameter. 2. Apply input validation and parameterized queries or prepared statements in the application code to sanitize the 'ID' parameter, preventing injection of malicious SQL commands. 3. Conduct thorough code audits and penetration testing focusing on SQL Injection vectors in the Restaurant Order System, especially on all user-supplied inputs. 4. Monitor database logs and web server logs for unusual query patterns or repeated failed attempts that may indicate exploitation attempts. 5. Segregate the database server from the internet and limit database user privileges to the minimum necessary to reduce the impact of a successful injection. 6. If possible, replace or upgrade the vulnerable software to a newer, patched version once available. 7. Educate staff about the risks of SQL Injection and ensure that security best practices are integrated into the software development lifecycle for any customizations or future deployments.

Description

A vulnerability, which was classified as critical, was found in code-projects Restaurant Order System 1.0. This affects an unknown part of the file /table.php. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…