CVE-2025-13793VulnerabilityPublished 30 Nov 2025Updated 1 Dec 2025

CVE-2025-13793: winston-dsouza Ecommerce-Website · Cross Site Scripting

Affects winston-dsouza Ecommerce-WebsiteSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 07:57 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 24% 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 30 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-26.

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

AI-suggested

1. Implement strict input validation and output encoding on the 'Error' GET parameter within /includes/header_menu.php to neutralize malicious scripts. 2. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 3. Conduct a comprehensive code review of all user input handling across the ecommerce platform to identify and remediate similar XSS vectors. 4. Monitor web server logs and application behavior for suspicious requests or patterns indicative of exploitation attempts. 5. Educate users and staff about phishing risks and encourage cautious behavior when interacting with unexpected URLs or messages. 6. If feasible, isolate or sandbox the vulnerable component to limit the impact of potential exploitation. 7. Engage with the vendor or consider migrating to alternative ecommerce solutions with active security support. 8. Regularly update web application firewalls (WAFs) with rules to detect and block XSS payloads targeting this parameter. 9. Implement multi-factor authentication to reduce the impact of session hijacking. 10. Maintain an incident response plan tailored to web application attacks to enable rapid containment and recovery.

Description

A weakness has been identified in winston-dsouza Ecommerce-Website up to 87734c043269baac0b4cfe9664784462138b1b2e. Affected by this issue is some unknown functionality of the file /includes/header_menu.php of the component GET Parameter Handler. Executing manipulation of the argument Error can lead to cross site scripting. The attack can be executed remotely. The exploit has been made available to the public and could be exploited. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, especially those operating e-commerce platforms using the winston-dsouza Ecommerce-Website software, this vulnerability poses a tangible risk to customer trust and data confidentiality. Exploitation could lead to session hijacking, enabling attackers to impersonate users and potentially access sensitive personal or payment information. Phishing attacks facilitated by injected scripts could further compromise user credentials or lead to financial fraud. The reputational damage and potential regulatory consequences under GDPR for failing to protect customer data could be significant. Additionally, the lack of vendor response and patches increases the window of exposure. Organizations relying on this software may face increased risk of targeted attacks, particularly in countries with high e-commerce penetration and digital payment adoption. The medium severity rating suggests that while the vulnerability is not critical, it is sufficiently serious to warrant prompt remediation to avoid exploitation and downstream impacts.

Summary

CVE-2025-13793 identifies a cross-site scripting (XSS) vulnerability in the winston-dsouza Ecommerce-Website product, specifically in the /includes/header_menu.php file's GET parameter 'Error'. This vulnerability arises from improper sanitization and validation of user-supplied input, allowing attackers to inject malicious JavaScript code that executes in the context of the victim's browser. The attack vector is remote and does not require authentication, but successful exploitation depends on user interaction, such as clicking a crafted URL. The product's rolling release model means version numbers are not clearly defined, complicating patch management and vulnerability tracking. The vendor has not responded to disclosure attempts, and no official patches are available, though exploit code has been publicly released, increasing the risk of exploitation. The CVSS 4.0 score of 5.3 reflects medium severity, with network attack vector, low complexity, no privileges required, and user interaction needed. The vulnerability primarily threatens the confidentiality and integrity of user sessions by enabling session hijacking, phishing, or defacement attacks, but does not directly impact system availability or escalate privileges. Given the ecommerce context, attackers could leverage this to steal customer data or disrupt business reputation.

References

Community reviews

Loading reviews…