CVE-2025-11603VulnerabilityPublished 11 Oct 2025Updated 17 Oct 2025

CVE-2025-11603: code-projects Simple Food Ordering System · SQL Injection

Affects code-projects Simple Food Ordering SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% 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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Oct 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-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projects Simple Food Ordering System	Affected =1.0	Fixed in–

AI-suggested

1. Immediately implement input validation and sanitization on the 'Category' parameter in /editproduct.php to prevent SQL injection. 2. Refactor the code to use parameterized queries or prepared statements instead of directly embedding user input into SQL commands. 3. Restrict database user permissions to the minimum necessary, limiting the potential damage from successful injection attacks. 4. Monitor web application logs for suspicious activity related to the 'Category' parameter or unexpected SQL errors. 5. If patching is not available, consider deploying a Web Application Firewall (WAF) with rules to detect and block SQL injection attempts targeting this endpoint. 6. Conduct a security audit of the entire application to identify and remediate similar injection vulnerabilities. 7. Educate developers on secure coding practices to prevent recurrence. 8. Regularly back up databases and ensure backups are secure to enable recovery in case of data tampering.

Description

A vulnerability was found in code-projects Simple Food Ordering System 1.0. This vulnerability affects unknown code of the file /editproduct.php. The manipulation of the argument Category results in sql injection. The attack may be launched remotely. The exploit has been made public and could be used.

Impact

For European organizations using the Simple Food Ordering System, this vulnerability could lead to unauthorized access to sensitive customer and business data stored in the backend database. Attackers could manipulate orders, alter product information, or extract confidential data, impacting data confidentiality and integrity. Although the availability impact is low, data manipulation could disrupt business operations and damage customer trust. The food service sector, including restaurants and catering services relying on this system, may face reputational damage and regulatory scrutiny under GDPR if personal data is compromised. The medium severity suggests that while the threat is not immediately critical, it poses a tangible risk that could be exploited by attackers with minimal effort. Organizations with limited IT security resources or those using outdated versions of the software are particularly vulnerable. The public availability of exploit code increases the likelihood of opportunistic attacks, especially in countries with high adoption of this software or similar platforms.

Summary

CVE-2025-11603 identifies an SQL injection vulnerability in the Simple Food Ordering System version 1.0 developed by code-projects. The flaw exists in the /editproduct.php script, where the 'Category' parameter is not properly sanitized or validated before being incorporated into SQL queries. This allows an unauthenticated remote attacker to inject arbitrary SQL commands, potentially leading to unauthorized data access, modification, or deletion within the backend database. The vulnerability does not require user interaction or elevated privileges, increasing its exploitability. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L - low privileges), no user interaction (UI:N), and low impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). Although the impact is limited, the exploitability is straightforward due to lack of authentication and input validation. The exploit code has been publicly disclosed, increasing the risk of exploitation, though no active exploitation has been reported to date. The absence of patches or official fixes necessitates immediate mitigation efforts by users of this software. The vulnerability highlights the critical need for secure coding practices, especially input validation and use of parameterized queries in web applications handling sensitive data such as food ordering systems.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Oct 2025, 14:26 UTC

Technical details

References

Community reviews

Related threats