VulnerabilityPublished 3 Mar 2026Updated 8 Oct 2026

CVE-2025-15599: cure53 DOMPurify · Cross-site Scripting

Affects cure53 DOMPurifySource CVE Database V5

Compare

Not known to be exploited · CVSS 5.1 Medium · fixed in 3.2.7 : update cure53 DOMPurify when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Active
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: Low
Subsequent system integrity: Low
Subsequent system availability: None

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: Active: Successful exploitation of this vulnerability requires a targeted user to perform specific, conscious interactions with the vulnerable system and the attacker’s payload, or the user’s interactions would actively subvert protection mechanisms which would lead to exploitation of the vulnerability.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system 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 Subsequent System.
Subsequent 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 Subsequent 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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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
cure53DOMPurify	Affected >=3.1.3 <=3.2.6 >=2.5.3 <=2.5.8	Fixed in–
npmdompurify`pkg:npm/dompurify`Other threats	Affected =3.1.3 =2.5.3	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade to DOMPurify version 3.2.7 or later for the 3.x branch to remediate this vulnerability. In the interim, developers should audit and sanitize any user input that might be embedded inside rawtext elements, especially <textarea>, using additional server-side validation and escaping techniques. Implement Content Security Policy (CSP) headers to restrict script execution and reduce the impact of potential XSS attacks. Conduct thorough code reviews and penetration testing focusing on input sanitization and output encoding. Educate developers about the risks of relying solely on client-side sanitization and encourage defense-in-depth strategies. Monitor web application logs and user reports for suspicious activity indicative of XSS exploitation attempts. Finally, maintain an inventory of all applications and libraries using DOMPurify to ensure timely updates and vulnerability management.

Description

DOMPurify 3.1.3 through 3.2.6 and 2.5.3 through 2.5.8 contain a cross-site scripting vulnerability that allows attackers to bypass attribute sanitization by exploiting missing textarea rawtext element validation in the SAFE_FOR_XML regex. Attackers can include closing rawtext tags like </textarea> in attribute values to break out of rawtext contexts and execute JavaScript when sanitized output is placed inside rawtext elements. The 3.x branch was fixed in 3.2.7; the 2.x branch was never patched.

Impact

This vulnerability allows attackers to execute arbitrary JavaScript in the context of affected web applications that use vulnerable DOMPurify versions to sanitize user input. Successful exploitation can lead to theft of sensitive information such as cookies, session tokens, or other credentials, enabling account takeover or further attacks like phishing or malware distribution. It can also allow attackers to manipulate the DOM, deface websites, or perform actions on behalf of the user. Given DOMPurify's popularity in securing web applications, a large number of websites and services could be affected globally. The impact is particularly critical for applications handling sensitive user data, financial transactions, or enterprise environments where trust boundaries are crucial. Although the vulnerability requires user interaction, the ease of exploitation via crafted web content or user-generated input makes it a moderate risk. The lack of a patch for the 2.x branch increases exposure for legacy systems. Organizations relying on vulnerable versions risk reputational damage, regulatory penalties, and operational disruption if exploited.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Mar 2026, 19:48 UTC

Technical details

References

Community reviews

Related threats