Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NSummary
CVE-2024-4439 is a high-severity Basic XSS (CWE-80) vulnerability in Wordpress Wordpress. Its CVSS base score is 7.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked in the top 0.7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
WordPress Core contains a stored cross-site scripting vulnerability in the Avatar block that affects versions through 6.5.2. The flaw stems from insufficient output escaping of user display names, allowing malicious script content to be persisted and later rendered when pages containing the block are viewed. The issue is tracked as CWE-80 and carries a CVSS 3.1 score of 7.2.
Authenticated users with contributor-level access or higher can exploit the weakness by setting a crafted display name that is stored and executed in the context of other visitors. Unauthenticated attackers can achieve the same outcome on any page that includes the comment block and displays the comment author’s avatar, resulting in arbitrary script execution with a scope that crosses security boundaries.
The WordPress 6.5.2 maintenance and security release addresses the issue through changesets that add proper escaping in the avatar block implementation. Administrators are advised to update immediately; the referenced Wordfence analysis and core Trac entries provide the specific code diffs applied to the 6.4 and main branches.
EPSS values have remained elevated, with a current score of 0.9058 and a recorded peak of 0.9206, indicating sustained exploitation interest following disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-44058
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.1V1.3.1V1.3.3V1.3.4
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover missing or incorrect neutralization of script tags through targeted XSS test cases.
Input validation explicitly requires checking and neutralizing untrusted web inputs containing script-related characters before they reach a downstream renderer.
Secure engineering principles include mandatory output encoding and neutralization of HTML metacharacters to stop injection at the source.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require output encoding and input validation that prevent basic XSS.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches unneutralized script tags before release.
Secure SDLC mandates input validation and output encoding that directly prevent basic XSS.
Application security requirements explicitly call for neutralization of script-related HTML tags.
Secure coding standards require proper escaping of <, >, & to block XSS.
Web filtering can block some reflected XSS payloads at the network edge.