Skip to content
OpenAdvisories
High · 7.2 Scanner template Public exploit CVE-2024-4439 EUVD-2024-44058GHSA-682x-vcqv-v7v6

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 …

Published May 3, 2024 · Updated Aug 1, 2024 · Assigned by Wordfence

Vendor: WordPress Product: WordPress Package: wordpress Package: wordpress Category: Web / CMS Ecosystem: Debian Ecosystem: Ubuntu

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.

Affected products

VendorProductAffectedFixed
WordPress Foundation WordPress 6.0 – ≤ 6.0.7, 6.1 – ≤ 6.1.5, 6.2 – ≤ 6.2.4, 6.3 – ≤ 6.3.3, 6.4 – ≤ 6.4.3, 6.5 – ≤ 6.5.1 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

Debian

Security tracker ↗
ReleasePackageFixed inAdvisory
Debian 14 wordpress 6.5.2+dfsg1-1 —
Debian 13 wordpress 6.5.2+dfsg1-1 —
Debian 12 wordpress 6.1.9+dfsg1-0+deb12u1 DSA-6075-1

Ubuntu

Security tracker ↗
ReleasePackageFixed inAdvisory
Ubuntu 24.04 LTS wordpress No fix yet —
Ubuntu 22.04 LTS wordpress No fix yet —
Ubuntu 20.04 LTS wordpress No fix yet —
Ubuntu 18.04 LTS wordpress No fix yet —
Ubuntu 16.04 LTS wordpress No fix yet —

Public exploits

Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.

Third-party code, not reviewed by us. Public PoCs are sometimes fake or contain malware. Read the code first and run it only in an isolated lab, against systems you are authorised to test.

GitHub 5 repositories

Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.

Automated scanner template

A ready-made Nuclei template detects this vulnerability automatically. Vulnerabilities with public scanner templates are typically probed across the internet soon after the template appears — exposed systems should be patched first.

Source: projectdiscovery/nuclei-templates (MIT) — updated daily. Only links are listed.

Advisories 2

References