CVE-2025-8018: code-projects Food Ordering Review System · SQL Injection
Affects code-projects Food Ordering Review SystemSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 08:30 UTC
- 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:PExploitation evidence
Disclosed: evidence found.
CVE published 22 Jul 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| code-projects Food Ordering Review System | Affected
| Fixed in– |
AI-suggested
European organizations should immediately audit their deployment of the code-projects Food Ordering Review System to identify if version 1.0 is in use. Since no official patches are currently available, organizations should implement the following specific mitigations: 1) Apply Web Application Firewall (WAF) rules tailored to detect and block SQL injection attempts targeting the 'reg_Id' parameter and other input fields on /user/reservation_page.php. 2) Employ parameterized queries or prepared statements in the application code to prevent injection if source code access and modification are possible. 3) Conduct thorough input validation and sanitization on all user-supplied data, especially parameters related to reservations and user input. 4) Restrict database user permissions to the minimum necessary to limit the impact of a successful injection. 5) Monitor logs for unusual database query patterns or errors indicative of injection attempts. 6) Consider isolating the affected system within the network to limit lateral movement. 7) Plan for an upgrade or replacement of the vulnerable software version once a patch or secure alternative is available. 8) Educate IT and security teams about the vulnerability and ensure incident response plans are updated to handle potential exploitation.
Description
A vulnerability was found in code-projects Food Ordering Review System 1.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /user/reservation_page.php. The manipulation of the argument reg_Id leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well.