CVE-2024-4439: WordPress · Cross-site Scripting
Affects WordPressSource CVE Database V5
Not known to be exploited · public detection template (Nuclei) · 71% EPSS · CVSS 7.2 High.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 71.0% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 14 May 2024
Detectable: evidence found.
nuclei template: WordPress Core <6.5.2 - Cross-Site Scripting
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-4439, organizations should promptly update WordPress to a patched version once available. In the interim, implement strict input validation and output escaping for user display names and comment author fields, particularly in the Avatar and comment blocks. Employ Web Application Firewalls (WAFs) with rules targeting XSS payloads in user display names and comments to block malicious requests. Disable or restrict the use of the Avatar block and comment avatars if feasible. Limit contributor-level user privileges and monitor user-generated content for suspicious scripts. Enable Content Security Policy (CSP) headers to reduce the impact of injected scripts by restricting script sources. Regularly audit and sanitize stored user inputs. Additionally, educate site administrators about the risks and signs of XSS exploitation to enable rapid detection and response.
Description
WordPress Core is vulnerable to Stored Cross-Site Scripting via user display names in the Avatar block in various versions up to 6.5.2 due to insufficient output escaping on the display name. 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. In addition, it also makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that have the comment block present and display the comment author's avatar.
References
- wordfence.com/threat-intel/vulnerabilities/id/e363c09a-4381-4b3a-951c-9a0ff5669016?source=cve (opens in a new tab)
- wordpress.org/news/2024/04/wordpress-6-5-2-maintenance-and-security-release/ (opens in a new tab)
- core.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=57950%40%2F&new=57950%40%2F&sfp_email=&sfph_mail= (opens in a new tab)
- core.trac.wordpress.org/changeset/57951/branches/6.4/src/wp-includes/blocks/avatar.php (opens in a new tab)
- wordfence.com/blog/2024/04/unauthenticated-stored-cross-site-scripting-vulnerability-patched-in-wordpress-core/ (opens in a new tab)