Skip to main content
CVE-2025-6123VulnerabilityPublished

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

Affects code-projects Restaurant Order SystemSource CVE Database V5

0

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

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 /payment.php endpoint via network-level controls such as firewalls or web application firewalls (WAFs) with SQL injection detection and prevention capabilities. 2. Implement strict input validation and parameterized queries or prepared statements in the application code to eliminate SQL injection vectors, focusing on sanitizing the 'tabidNoti' parameter. 3. Conduct a thorough code review of the entire application to identify and remediate any other injection points or insecure coding practices. 4. Monitor logs for unusual or suspicious requests targeting the 'tabidNoti' parameter or /payment.php endpoint to detect potential exploitation attempts. 5. If possible, isolate the affected system from critical network segments until a patch or update is available. 6. Engage with the vendor or community to obtain or develop patches or updated versions that address this vulnerability. 7. Educate staff on the risks and signs of exploitation to improve incident response readiness. 8. As a longer-term measure, consider migrating to more secure and actively maintained restaurant order management platforms with robust security practices.

Description

A vulnerability has been found in code-projects Restaurant Order System 1.0 and classified as critical. This vulnerability affects unknown code of the file /payment.php. The manipulation of the argument tabidNoti leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…