CVE-2025-6124: code-projects Restaurant Order System · SQL Injection
Affects code-projects Restaurant Order SystemSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- 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:PExploitation evidence
Disclosed: evidence found.
CVE published 16 Jun 2025
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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| code-projects Restaurant Order System | Affected
| Fixed in– |
AI-suggested
1. Immediate mitigation should focus on isolating the vulnerable system from public networks to reduce exposure until a patch is available. 2. Implement Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the 'ID' parameter in /tablelow.php. 3. Conduct a thorough code review and input validation on all parameters, especially 'ID', to ensure proper sanitization and use of parameterized queries or prepared statements. 4. If possible, upgrade or replace the Restaurant Order System with a version that addresses this vulnerability or switch to a more secure alternative. 5. Monitor logs for unusual database query patterns or repeated access attempts to /tablelow.php that could indicate exploitation attempts. 6. Educate IT staff and administrators about this vulnerability and establish incident response plans tailored to potential SQL injection attacks. 7. Regularly back up databases and ensure backups are stored securely to enable recovery in case of data corruption or loss. 8. Engage with the vendor or community to obtain patches or security advisories promptly once they become available.
Description
A vulnerability was found in code-projects Restaurant Order System 1.0 and classified as critical. This issue affects some unknown processing of the file /tablelow.php. The manipulation of the argument ID leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.