Technical impact
Happy DOM, a headless browser implementation, automatically loads iframe src URLs and link rel="stylesheet" href URLs while parsing untrusted HTML on the server. Because the options disableIframePageLoading and disableCSSFileLoading default to false in versions prior to 21.0.0, an attacker who can supply or influence the HTML that Happy DOM parses can cause the server to send requests to any arbitrary internal or cloud endpoint. The responses from those endpoints may include confidential data, credentials, or expose internal network topology, allowing information disclosure and potential credential theft. The weakness is a classic Server‑Side Request Forgery (CWE‑918).
Affected Systems
The affected product is Happy DOM from the vendor capricorn86. All releases before version 21.0.0 are vulnerable. The issue was fixed in Happy DOM 21.0.0; any installation still running an earlier release should be upgraded.
Risk and Exploitability
The CVSS score of 8.6 places the vulnerability in the High severity range, indicating that exploitation could seriously compromise confidentiality and integrity. The EPSS score is not available, so the current likelihood of exploitation is uncertain, but because the vulnerability can be triggered via any untrusted HTML input, it poses a realistic risk for applications that parse untrusted content server‑side. The vulnerability is not listed in CISA’s KEV catalog as of the latest advisory. Attackers would need to deliver malicious HTML to the application – for example, through a form or API that accepts rich content – and rely on Happy DOM’s default behavior to initiate outbound requests without restricting the target domain.
Github GHSA