CVE-2025-63883VulnerabilityPublished 18 Nov 2025

CVE-2025-63883: n/a

Source CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 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

European organizations should immediately audit their electic-shop v1.0 deployments for unsafe DOM insertion patterns, specifically usage of innerHTML, insertAdjacentHTML, and document.write with untrusted inputs. Implement strict input validation and sanitization on all client-side inputs derived from URLs or fragments. Employ context-aware encoding libraries such as DOMPurify or similar to sanitize HTML content before insertion. Consider refactoring client-side code to use safer DOM manipulation methods like textContent or createElement combined with setAttribute to avoid direct HTML injection. Educate developers on secure coding practices to prevent DOM-based XSS. Deploy Content Security Policy (CSP) headers with strict script-src directives to reduce the impact of injected scripts. Monitor web traffic for suspicious URL patterns and user reports of unexpected behavior. Since no official patches are available, organizations should consider isolating vulnerable components or temporarily disabling features that rely on unsafe DOM insertion until fixes are released. Conduct regular security testing, including automated scanning and manual penetration testing focused on client-side vulnerabilities. Finally, raise user awareness about phishing risks associated with clicking unknown links.

Description

CVE-2025-63883 is a DOM-based cross-site scripting (XSS) vulnerability in the electic-shop v1.0 e-commerce platform. The vulnerability arises because client-side JavaScript unsafely inserts attacker-controlled input into the DOM using innerHTML, insertAdjacentHTML, or document.write without proper sanitization or encoding. An attacker can craft a malicious URL that executes arbitrary JavaScript in the victim's browser under the electic-shop origin when visited. This vulnerability requires user interaction (clicking the malicious link) but does not require authentication. The CVSS score is 5.4 (medium severity), reflecting limited confidentiality and integrity impact and no availability impact. No known exploits are currently reported in the wild. European organizations using electic-shop v1.

Impact

For European organizations using electic-shop v1.0, this vulnerability poses a moderate risk primarily to confidentiality and integrity of user data. Attackers exploiting this vulnerability can steal session cookies or other sensitive information accessible via JavaScript, potentially leading to account hijacking or fraud. The integrity of the web page can be compromised by injecting malicious scripts that alter content or behavior, potentially damaging brand reputation and user trust. Since the vulnerability requires user interaction, phishing or social engineering campaigns may be used to lure victims to malicious URLs. Although availability is not impacted, the indirect effects of compromised user accounts or data leakage can be significant. E-commerce platforms are critical infrastructure for many European businesses, and exploitation could lead to financial losses, regulatory penalties under GDPR for data breaches, and erosion of customer confidence. The lack of available patches increases the urgency for organizations to implement mitigations. The threat is more pronounced for organizations with high web traffic and those that rely heavily on client-side scripting for dynamic content rendering.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
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.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/minhajultaivin/security-advisories/blob/main/CVE-2025-63883.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 25 Nov 2025, 15:26 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats