Skip to main content
CVE-2024-26466VulnerabilityPublished Updated

CVE-2024-26466: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% 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:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Feb 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

AI-suggested

To mitigate CVE-2024-26466, organizations and developers using web-platform-tests should: 1) Monitor the official web-platform-tests repository and security advisories for patches or updates addressing this vulnerability and apply them promptly once available. 2) Restrict access to the vulnerable /dom/ranges/Range-test-iframe.html component and related test files to trusted users only, minimizing exposure to untrusted or external users. 3) Educate users involved in testing about the risks of interacting with untrusted URLs or links that could exploit this DOM-based XSS vulnerability. 4) Implement Content Security Policy (CSP) headers in testing environments to limit the execution of unauthorized scripts and reduce the impact of potential XSS attacks. 5) Consider sandboxing or isolating the testing environment to prevent any malicious script execution from affecting other systems or networks. 6) Review and harden the input handling and DOM manipulation code in custom test components to prevent similar vulnerabilities. 7) Use browser security features and extensions that can detect or block XSS attempts during testing. These steps go beyond generic advice by focusing on controlling access, user awareness, and environment isolation specific to the testing context.

Description

A DOM based cross-site scripting (XSS) vulnerability in the component /dom/ranges/Range-test-iframe.html of web-platform-tests/wpt before commit 938e843 allows attackers to execute arbitrary Javascript via sending a crafted URL.

References

Community reviews

Loading reviews…