CVE-2025-13571VulnerabilityPublished 23 Nov 2025

CVE-2025-13571: 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 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.3% chance of exploitation in 30 days – higher than 26% 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 23 Nov 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.

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 strict input validation and sanitization on the 'ID' parameter in /listorder.php to prevent SQL injection. 2. Refactor database queries to use prepared statements or parameterized queries, eliminating direct concatenation of user inputs into SQL commands. 3. Conduct a comprehensive code review of the entire application to identify and remediate other potential injection points. 4. Monitor network traffic and application logs for suspicious activities targeting the ordering system, focusing on unusual parameter values or error messages indicative of injection attempts. 5. Isolate the ordering system within a segmented network zone to limit lateral movement if compromised. 6. Apply web application firewalls (WAFs) with rules to detect and block SQL injection patterns targeting the affected endpoint. 7. Engage with the vendor or community to obtain patches or updates as soon as they become available. 8. Educate development and operations teams on secure coding practices and the importance of timely vulnerability management. 9. Regularly backup databases and test restoration procedures to minimize impact from potential data corruption or deletion.

Description

A vulnerability was determined in code-projects Simple Food Ordering System 1.0. Affected by this issue is some unknown functionality of the file /listorder.php. Executing manipulation of the argument ID can lead to sql injection. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized.

Impact

For European organizations using the Simple Food Ordering System 1.0, this vulnerability poses a risk of unauthorized data access and manipulation, potentially leading to breaches of customer personal and payment information. This can result in reputational damage, regulatory penalties under GDPR for data protection failures, and operational disruptions if the ordering system is compromised or taken offline. The food service sector, including restaurants and catering businesses, may experience service interruptions affecting customer trust and revenue. Additionally, attackers could leverage the vulnerability to pivot into internal networks if the ordering system is connected to broader IT infrastructure. The medium severity indicates a moderate but tangible threat, especially for SMEs that may lack robust cybersecurity defenses. The absence of known exploits currently provides a window for proactive mitigation before active attacks emerge.

Summary

CVE-2025-13571 identifies a SQL injection vulnerability in the Simple Food Ordering System version 1.0 developed by code-projects. The vulnerability is located in the /listorder.php script, specifically in the handling of the 'ID' parameter. An attacker can remotely manipulate this parameter to inject arbitrary SQL commands into the backend database query. This injection flaw allows unauthorized access to database contents, potentially leading to data leakage, unauthorized data modification, or deletion. The vulnerability does not require user interaction or authentication, making it easier to exploit remotely over the network. The CVSS 4.0 base score is 5.3 (medium), reflecting the moderate impact on confidentiality, integrity, and availability, with low attack complexity and no privileges required. Although no known exploits are currently active in the wild, the public disclosure of the vulnerability increases the risk of exploitation by attackers. The lack of available patches at the time of disclosure necessitates immediate mitigation through secure coding practices and input validation. This vulnerability is particularly critical for organizations relying on this software for order management, as exploitation could disrupt business operations and compromise customer data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Nov 2025, 23:07 UTC

Technical details

References

Community reviews

Related threats