CVE-2025-13203VulnerabilityPublished 15 Nov 2025Updated 17 Nov 2025

CVE-2025-13203: code-projects Simple Cafe Ordering System · SQL Injection

Affects code-projects Simple Cafe Ordering SystemSource CVE Database V5

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 36% 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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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 15 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
GitHubcode-projects/SimpleCafe`pkg:github/code-projects/SimpleCafe`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-13203, organizations should immediately audit the Simple Cafe Ordering System installations and restrict external access to the /addmem.php endpoint where possible. Developers must implement strict input validation and sanitization on the studentnum parameter, preferably using prepared statements or parameterized queries to prevent SQL injection. If source code modification is not feasible, deploying a Web Application Firewall (WAF) with SQL injection detection rules can provide a temporary protective layer. Regularly monitoring logs for suspicious database query patterns or unusual access attempts is recommended. Organizations should also consider isolating the affected system within segmented network zones to limit potential lateral movement. Since no official patches are available, organizations should engage with the vendor or community for updates and consider migrating to more secure ordering systems if remediation is delayed. Finally, ensuring backups of critical data are current will aid recovery if exploitation occurs.

Description

A weakness has been identified in code-projects Simple Cafe Ordering System 1.0. This vulnerability affects unknown code of the file /addmem.php. Executing manipulation of the argument studentnum can lead to sql injection. It is possible to launch the attack remotely. The exploit has been made available to the public and could be exploited.

Impact

For European organizations, especially small businesses, educational institutions, or cafes using the Simple Cafe Ordering System, this vulnerability poses a risk of unauthorized access to sensitive customer or student data, including personal identifiers and order information. Exploitation could lead to data breaches, reputational damage, and potential regulatory penalties under GDPR due to improper data protection. Additionally, attackers could alter or delete order data, disrupting business operations and causing financial losses. Since the vulnerability allows remote exploitation without authentication, attackers can target exposed systems directly, increasing the likelihood of compromise. The medium severity indicates that while the impact is not catastrophic, it is significant enough to warrant prompt remediation to avoid escalation or lateral movement within networks. European entities relying on similar PHP-based web applications may also face analogous risks if similar coding practices are present.

Summary

CVE-2025-13203 identifies a SQL injection vulnerability in the Simple Cafe Ordering System version 1.0 developed by code-projects. The vulnerability resides in the /addmem.php script, where the studentnum parameter is improperly sanitized, allowing attackers to inject malicious SQL code. This injection flaw enables remote attackers to manipulate backend database queries without requiring authentication or user interaction, potentially leading to unauthorized data disclosure, data modification, or even complete compromise of the database. The vulnerability is exploitable over the network, increasing its attack surface. The CVSS 4.0 base score is 6.9, reflecting a medium severity due to the ease of exploitation (no privileges or user interaction needed) but limited impact scope (confidentiality, integrity, and availability impacts are low to limited). Although no known exploits are currently active in the wild, public availability of exploit code raises the risk of future attacks. The affected software is a PHP-based ordering system commonly used in small cafes or educational environments, which may store sensitive customer or student data. The lack of official patches or vendor advisories necessitates immediate attention from users to implement input validation and parameterized queries to mitigate the risk.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Nov 2025, 18:27 UTC

Technical details

References

Community reviews

Related threats