Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12333: Cross Site Scripting in code-projects E-Commerce Website

0
Medium
VulnerabilityCVE-2025-12333cvecve-2025-12333
Published: Mon Oct 27 2025 (10/27/2025, 22:32:08 UTC)
Source: CVE Database V5
Vendor/Project: code-projects
Product: E-Commerce Website

Description

A vulnerability has been found in code-projects E-Commerce Website 1.0. This impacts an unknown function of the file /pages/supplier_add.php. The manipulation of the argument supp_name/supp_address leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

AI-Powered Analysis

AILast updated: 11/04/2025, 03:15:03 UTC

Technical Analysis

CVE-2025-12333 is a Cross Site Scripting (XSS) vulnerability identified in version 1.0 of the code-projects E-Commerce Website, specifically within the /pages/supplier_add.php script. The vulnerability arises due to insufficient sanitization of user-supplied input in the supp_name and supp_address parameters, which are reflected in the web page output without proper encoding or filtering. This flaw enables an attacker to inject arbitrary JavaScript code that executes in the context of a victim’s browser when they visit a crafted URL or interact with manipulated input fields. The attack vector is remote and does not require any authentication or privileges, though it requires user interaction to trigger the malicious script. The CVSS 4.0 base score of 5.3 reflects a medium severity, considering the ease of exploitation (low complexity, no privileges needed), but limited impact on confidentiality and availability. The vulnerability could be leveraged for session hijacking, credential theft, or delivering further malware via drive-by downloads. Although no active exploits have been reported in the wild, the public disclosure increases the risk of opportunistic attacks. The absence of vendor patches or official remediation guidance necessitates defensive measures by administrators. This vulnerability highlights the importance of secure coding practices such as input validation, output encoding, and the use of security headers like Content Security Policy (CSP) to mitigate XSS risks in web applications.

Potential Impact

For European organizations using the affected code-projects E-Commerce Website 1.0, this vulnerability poses a risk of client-side attacks that can compromise user sessions, steal sensitive information, or facilitate phishing and social engineering campaigns. Given the e-commerce context, attackers could impersonate legitimate suppliers or customers, potentially disrupting business operations and damaging brand reputation. The impact on confidentiality is moderate due to potential theft of session cookies or personal data, while integrity could be compromised through unauthorized script execution altering displayed content. Availability impact is minimal as the vulnerability does not directly affect server stability. However, successful exploitation could lead to indirect denial of service through user distrust or account lockouts. European organizations with significant online supplier or customer interactions are particularly vulnerable. The public disclosure and ease of exploitation increase the urgency for mitigation, especially in countries with large e-commerce markets or where this platform is widely deployed.

Mitigation Recommendations

1. Immediate implementation of input validation on the supp_name and supp_address parameters to reject or sanitize malicious input before processing. 2. Apply proper output encoding (e.g., HTML entity encoding) when reflecting user input in web pages to prevent script execution. 3. Deploy a strict Content Security Policy (CSP) header to restrict the execution of unauthorized scripts and reduce the impact of XSS attacks. 4. Conduct a thorough code review of the entire application to identify and remediate other potential XSS or injection points. 5. If possible, upgrade to a patched version of the software once available or apply vendor-provided fixes. 6. Educate users and administrators about the risks of clicking on suspicious links and encourage the use of browser security features. 7. Monitor web server logs and user reports for signs of exploitation attempts or unusual activity related to supplier input forms. 8. Consider implementing Web Application Firewalls (WAF) with rules to detect and block common XSS payloads targeting the affected parameters.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-10-27T12:38:29.215Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68fff444ba6dffc5e21326a1

Added to database: 10/27/2025, 10:37:56 PM

Last enriched: 11/4/2025, 3:15:03 AM

Last updated: 12/10/2025, 4:43:38 AM

Views: 121

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats