dbcve.org
WordPressCMS

CVE-2024-4439

MEDIUM · 6.1 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to after 6.5.1 or later.
See remediation →
68/100
Remediation priority · Elevated
High EPSS Public exploit Remotely reachable No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WordPressCMS
Affected:>= 6.0, <= 6.0.7>= 6.1, <= 6.1.5>= 6.2, <= 6.2.4>= 6.3, <= 6.3.3>= 6.4.0, <= 6.4.3>= 6.5, <= 6.5.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 6.5.1
Vendor patch core.trac.wordpress.org →
Recommended fix High confidence

WordPress 6.5.3 (or latest stable 6.x release)

  1. 1. Back up your WordPress database and files before performing any upgrade.
  2. 2. Ensure you have administrator access to perform the upgrade.
  3. 3. Navigate to Dashboard > Updates in the WordPress admin panel.
  4. 4. Click 'Update Now' to upgrade to the latest WordPress version (6.5.3 or later).
  5. 5. Alternatively, download WordPress from wordpress.org and upgrade via FTP/SFTP if automatic updates are not available.
  6. 6. Verify the upgrade was successful by checking the WordPress version at Dashboard > At a Glance.
  7. 7. Clear any caching plugins or server-side caches after the upgrade.
Caveat Standard WordPress minor version upgrades typically have no breaking changes; minor updates include security fixes and are backward compatible

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4439 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-4439 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data