CVE-2025-12299VulnerabilityPublished 27 Oct 2025

CVE-2025-12299: 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 33% 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-12299, organizations should immediately implement strict input validation and output encoding on the pname, category, and price parameters within /addproduct.php. Employing a whitelist approach for acceptable input values can significantly reduce injection risks. Utilizing security libraries or frameworks that automatically handle XSS protections is recommended. Web Application Firewalls (WAFs) can be configured to detect and block suspicious input patterns targeting these parameters. Monitoring web server logs for unusual requests to /addproduct.php can help identify attempted exploits. Educating staff and users about the risks of clicking unknown links can reduce successful exploitation. Finally, applying Content Security Policy (CSP) headers can limit the impact of injected scripts by restricting script execution sources.

Description

CVE-2025-12299 is a medium severity cross-site scripting (XSS) vulnerability found in version 1.0 of the code-projects Simple Food Ordering System. The flaw exists in the /addproduct.php file, where manipulation of the pname, category, or price parameters allows remote attackers to inject malicious scripts. Exploitation does not require authentication but does require user interaction, such as a victim visiting a crafted URL. Although no known exploits are currently observed in the wild, the exploit code has been publicly released, increasing the risk of attacks. The vulnerability can lead to theft of user credentials, session hijacking, or defacement of web content. European organizations using this software, especially in the hospitality or food service sectors, may face targeted attacks. Mitigation involves sanitizing and validating all user inputs on the affected parameters and applying patches once available. Countries with higher adoption of small to medium hospitality businesses using this software, such as Germany, France, Italy, and Spain, are more likely to be impacted.

Impact

For European organizations, especially those in the hospitality and food service sectors using the Simple Food Ordering System, this vulnerability could lead to significant security incidents. Successful exploitation could result in theft of customer credentials, unauthorized access to user sessions, and potential defacement or manipulation of the ordering interface, undermining customer trust and business reputation. Additionally, attackers could use the vulnerability as a foothold for further attacks such as phishing or spreading malware. Given the public availability of exploit code, the risk of targeted attacks is elevated. The impact on data privacy is particularly concerning under the GDPR framework, as compromised customer data could lead to regulatory penalties and legal liabilities. Organizations relying on this software without timely mitigation may face service disruptions and financial losses due to fraud or remediation costs.

Summary

CVE-2025-12299 is a cross-site scripting vulnerability identified in the Simple Food Ordering System version 1.0 developed by code-projects. The vulnerability resides in the /addproduct.php script, where the parameters pname, category, and price are not properly sanitized or validated, allowing attackers to inject malicious JavaScript code. This flaw enables remote attackers to craft URLs or requests that, when visited or processed by a victim's browser, execute arbitrary scripts in the context of the vulnerable web application. The vulnerability requires no authentication and can be exploited remotely, but user interaction is necessary for the attack to succeed (e.g., clicking a malicious link). The CVSS 4.0 vector indicates low attack complexity and no privileges required, but user interaction is needed. The impact primarily affects confidentiality and integrity by enabling session hijacking, credential theft, or manipulation of displayed content. Although no patches or fixes have been officially released yet, the public availability of exploit code increases the urgency for mitigation. The vulnerability is particularly relevant for organizations running this software in production environments, especially those handling customer data or payment information. Proper input validation, output encoding, and use of security headers are critical to mitigating this threat.

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