CVE-2025-66021
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-11-26

Last updated on: 2025-12-30

Assigner: GitHub, Inc.

Description
OWASP Java HTML Sanitizer is a configureable HTML Sanitizer written in Java, allowing inclusion of HTML authored by third-parties in web applications while protecting against XSS. In version 20240325.1, OWASP java html sanitizer is vulnerable to XSS if HtmlPolicyBuilder allows noscript and style tags with allowTextIn inside the style tag. This could lead to XSS if the payload is crafted in such a way that it does not sanitise the CSS and allows tags which is not mentioned in HTML policy. At time of publication no known patch is available.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-11-26
Last Modified
2025-12-30
Generated
2026-05-06
AI Q&A
2025-11-26
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
owasp java_html_sanitizer 20240325.1
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.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability affects the OWASP Java HTML Sanitizer version 20240325.1. It occurs when the HtmlPolicyBuilder configuration allows 'noscript' and 'style' tags with the 'allowTextIn' option inside the style tag. This improper sanitization can lead to Cross-Site Scripting (XSS) attacks if an attacker crafts a payload that bypasses CSS sanitization and includes tags not covered by the HTML policy.


How can this vulnerability impact me? :

The vulnerability can lead to Cross-Site Scripting (XSS) attacks, which may allow attackers to execute malicious scripts in the context of a user's browser. This can result in theft of user data, session hijacking, defacement of web content, or other malicious actions that compromise the security and integrity of the affected web application.


What immediate steps should I take to mitigate this vulnerability?

Since no known patch is available at the time of publication, immediate mitigation steps include reviewing and modifying the HtmlPolicyBuilder configuration to avoid allowing noscript and style tags with allowTextIn inside the style tag, thereby preventing unsafe CSS and tag inclusion that could lead to XSS. Additionally, consider implementing additional input validation and output encoding to reduce XSS risks until a patch is released.


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