CVE-2024-6307: WordPress · Cross-site Scripting
Affects WordPressSource CVE Database V5
Not known to be exploited · CVSS 6.4 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 2024
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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WordPress Foundation WordPress | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2024-6307, organizations should immediately update WordPress installations to version 6.5.5 or later, where the vulnerability is patched. Until updates can be applied, restrict contributor-level and higher permissions to trusted users only, minimizing the risk of malicious script injection. Implement strict content moderation policies and regularly audit pages for suspicious or unexpected script content. Employ web application firewalls (WAFs) with robust XSS detection and blocking capabilities to intercept malicious payloads. Enable security plugins that sanitize user inputs and monitor for anomalous behavior. Educate contributors about safe content practices and the risks of injecting untrusted code. Additionally, consider implementing Content Security Policy (CSP) headers to limit the execution of unauthorized scripts. Regular backups and incident response plans should be in place to quickly recover from potential compromises.
Description
WordPress Core is vulnerable to Stored Cross-Site Scripting via the HTML API in various versions prior to 6.5.5 due to insufficient input sanitization and output escaping on URLs. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.