CVE-2025-12298VulnerabilityPublished 27 Oct 2025

CVE-2025-12298: code-projects Simple Food Ordering System · Cross Site Scripting

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 32% 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:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
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: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within 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: None: There is no impact to availability within 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 27 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-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

To mitigate CVE-2025-12298, European organizations should implement the following specific measures: 1) Apply input validation on the pname parameter to reject or sanitize any input containing script tags or suspicious characters before processing. 2) Implement context-appropriate output encoding (e.g., HTML entity encoding) to ensure that any user-supplied data rendered in the web page cannot be interpreted as executable code. 3) Deploy a web application firewall (WAF) configured to detect and block common XSS attack patterns targeting the affected endpoint. 4) If possible, upgrade to a patched version of the Simple Food Ordering System once available or apply vendor-provided patches promptly. 5) Conduct security awareness training for staff to recognize phishing attempts that may leverage this vulnerability. 6) Regularly audit and monitor web application logs for suspicious activities related to the /editcategory.php endpoint. 7) Consider implementing Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. These targeted actions go beyond generic advice and address the root cause and exploitation vectors specific to this vulnerability.

Description

CVE-2025-12298 is a medium severity cross-site scripting (XSS) vulnerability in version 1.0 of the code-projects Simple Food Ordering System, specifically in the /editcategory.php file via the pname parameter. The vulnerability allows remote attackers to inject malicious scripts without requiring authentication, though user interaction is needed to trigger the attack. Exploits are publicly available, increasing the risk of exploitation. While no known active exploitation has been reported, affected systems remain vulnerable. The impact primarily concerns client-side attacks such as session hijacking, credential theft, or defacement. European organizations using this software, especially in the food service sector, should prioritize patching or mitigating this issue. Countries with higher adoption of this product or with strategic food service industries are more likely to be affected. Mitigations include input validation, output encoding, and deploying web application firewalls tailored to detect XSS payloads.

Impact

For European organizations, the impact of this vulnerability can be significant, particularly for small and medium enterprises in the food service sector that rely on the Simple Food Ordering System. Exploitation could lead to client-side attacks such as session hijacking, enabling attackers to impersonate legitimate users, potentially leading to unauthorized order manipulation or data exposure. It could also facilitate phishing attacks by injecting malicious content into trusted web pages, damaging customer trust and brand reputation. While the vulnerability does not directly compromise server-side data or availability, the indirect effects on confidentiality and integrity of user sessions and data are notable. Additionally, regulatory frameworks like GDPR impose strict requirements on protecting customer data, and exploitation of this vulnerability could result in compliance violations and financial penalties. The medium severity indicates that while the threat is not critical, it should not be ignored, especially given the availability of exploit code and the remote attack vector.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 17:51 UTC

Technical details

References

Community reviews

Related threats