CVE-2024-4439: WordPress Core is vulnerable to Stored Cross-Site Scripting via user display names in the Avatar block in vari

Q: How do I fix CVE-2024-4439?

wordpress: upgrade to newer than 6.5.1. Exact commands for each OS are on this page.

Q: Is CVE-2024-4439 being exploited?

CVE-2024-4439 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-4439 affect?

CVE-2024-4439 affects wordpress. Severity is high (CVSS 7.2). 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 attacke

Q: How urgent is CVE-2024-4439?

Priority 60/100. High severity; EPSS top 1%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.2REMOTEUPGRADE

CVE-2024-4439 is a high-severity flaw (CVSS 7.2) affecting wordpress. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 atta

Why this priority

High severity
EPSS top 1%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	71.0% (top 1%)
CISA exploited list	No
Weakness	CWE-80
Published	2024-05-03
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: wordpress

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-05-03 06:15 UTCPublished CVE record published
2026-06-17 08:01 UTCUpdated Record last modified

wordpress wordpress UPGRADE

Affected: >= 6.0 and <= 6.0.7 · >= 6.1 and <= 6.1.5 · >= 6.2 and <= 6.2.4 · >= 6.3 and <= 6.3.3 · >= 6.4.0 and <= 6.4.3 · >= 6.5 and <= 6.5.1

Fixed in: newer than 6.5.1

Safe to downgrade to: a release before 6.0

1. Check installed version

apt-cache policy wordpress || rpm -q wordpress || wordpress --version

2. UPGRADE to newer than 6.5.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wordpress

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wordpress

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 6.0 (Debian / Ubuntu)

apt-cache madison wordpress sudo apt install wordpress=<VERSION_BEFORE_6.0> sudo apt-mark hold wordpress

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list wordpress sudo dnf downgrade wordpress-<VERSION_BEFORE_6.0> sudo dnf versionlock add wordpress

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Nuclei scan template: WordPress Core <6.5.2 - Cross-Site Scripting

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-4439?

wordpress: upgrade to newer than 6.5.1. Exact commands for each OS are on this page.

Is CVE-2024-4439 being exploited?

CVE-2024-4439 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-4439 affect?

CVE-2024-4439 affects wordpress. Severity is high (CVSS 7.2). 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 attacke

How urgent is CVE-2024-4439?

Priority 60/100. High severity; EPSS top 1%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2026-63030 CRITICAL 9.8 EXPLOITED UPGRADE WordPress Core Interpretation Conflict Vulnerability
CVE-2026-60137 MEDIUM 5.9 EXPLOITED UPGRADE WordPress Core SQL Injection Vulnerability
CVE-2023-39999 MEDIUM 4.3 UPGRADE MITIGATE Exposure of Sensitive Information to an Unauthorized Actor in WordPress from 6.3 through 6.3.1, from 6.2 throu
CVE-2026-87902 HIGH 8.1 EXPLOITED UPGRADE WordPress Core Remote File Inclusion Vulnerability
CVE-2024-31211 MEDIUM 5.5 UPGRADE WordPress is an open publishing platform for the Web

References

← Back to latest CVEs