CVE-2025-12299
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-27

Last updated on: 2026-04-29

Assigner: VulDB

Description
A security flaw has been discovered in code-projects Simple Food Ordering System 1.0. This vulnerability affects unknown code of the file /addproduct.php. The manipulation of the argument pname/category/price results in cross site scripting. It is possible to launch the attack remotely. The exploit has been released to the public and may be exploited.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-27
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2025-10-27
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
fabian simple_food_ordering_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
CWE-94 The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-12299 is a stored Cross-Site Scripting (XSS) vulnerability in version 1.0 of the Simple Food Ordering System, specifically in the addproduct.php file. It occurs because user inputs in the parameters pname, category, and price are not properly sanitized or encoded before being stored and displayed. This allows attackers to inject malicious JavaScript code that executes in the browsers of users who view the affected pages, potentially compromising data integrity and user security. The attack can be performed remotely without authentication but requires some user interaction. [1, 2, 3]


How can this vulnerability impact me? :

This vulnerability can lead to serious security impacts including session hijacking, account takeover, data theft, phishing attacks, malware distribution, and website defacement. Since the malicious scripts execute in the context of users' browsers, attackers can steal sensitive information or perform unauthorized actions on behalf of users. The vulnerability affects all major browsers and can be exploited remotely without authentication, making it a significant risk for users and administrators of the affected system. [2, 3]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by identifying the presence of the vulnerable 'addproduct.php' page in the Simple Food Ordering System and testing the input parameters 'pname', 'category', and 'price' for cross-site scripting (XSS) payloads. One method is to use Google dorking with the query 'inurl:addproduct.php' to find potentially vulnerable targets. Additionally, sending crafted POST requests with XSS payloads (e.g., <script>alert(1)</script>) to the 'addproduct.php' or 'editproduct.php' endpoints and observing if the script executes in the browser can confirm the vulnerability. Network captures showing malicious script execution or server logs confirming payload delivery can also help detect exploitation. No specific commands are provided, but tools like curl or Burp Suite can be used to send test payloads and monitor responses. [1, 2]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include implementing context-aware output encoding such as using PHP's htmlspecialchars function with ENT_QUOTES and UTF-8 when displaying user input to prevent script execution. Applying strict Content Security Policy (CSP) headers with nonce- or hash-based inline script restrictions is recommended. Input validation with whitelists to reject suspicious patterns should be enforced. Security headers like X-Content-Type-Options: nosniff, X-Frame-Options: DENY, and X-XSS-Protection: 1; mode=block should be used. Deploying Web Application Firewall (WAF) rules to detect and block XSS attempts, using modern web frameworks with built-in XSS protections, conducting developer security training, automated security testing, and regular audits are also advised. If possible, replacing the affected product with an alternative solution is suggested as no official patch is documented. [2, 3]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart