Skip to content
Fencer Vulns
medium 6.4

CVE-2024-6307 json

WordPress Core < 6.5.5 - Authenticated (Contributor+) Stored Cross-Site Scripting via HTML API

published 2024-06-25 2 y ago modified 2026-06-17 4 mo ago also BIT-wordpress-2024-6307 , BIT-wordpress-multisite-2024-6307 , EUVD-2024-47423

cvss
6.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits
0
none known

Summary

WordPress Core is vulnerable to Stored Cross-Site Scripting via the HTML API in various versions prior to 6.5.5 due to insufficient input sanitization and output escaping on URLs. 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.

Patch / fix

  • bitnami wordpress 5.9.10, 6.0.9, 6.1.7, 6.2.5, 6.3.5, 6.4.5, 6.5.5
  • bitnami wordpress-multisite 5.9.10, 6.0.9, 6.1.7, 6.2.5, 6.3.5, 6.4.5, 6.5.5
  • wordpress wordpress 5.9.10, 6.0.9, 6.1.7, 6.2.5, 6.3.5, 6.4.5, 6.5.5
  • johnpbloch wordpress-core 5.9.10, 6.0.9, 6.1.7, 6.2.5, 6.3.5, 6.4.5, 6.5.5
  • wordpress Debian 12 6.1.9+dfsg1-0+deb12u1
  • wordpress Debian 14, Debian 13 6.5.5+dfsg1-1

debian advisories DEBIAN-CVE-2024-6307

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-6307 updated cvss 6.4

wordpress: multiple vulnerabilities

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.47% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
OSV 3.1 6.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
bitnami wordpress
>=5.9.0, <5.9.10
>=6.0.0, <6.0.9
>=6.1.0, <6.1.7
>=6.2.0, <6.2.5
>=6.3.0, <6.3.5
>=6.4.0, <6.4.5
>=6.5.0, <6.5.5
5.9.10
6.0.9
6.1.7
6.2.5
6.3.5
6.4.5
6.5.5
bitnami wordpress-multisite
>=5.9.0, <5.9.10
>=6.0.0, <6.0.9
>=6.1.0, <6.1.7
>=6.2.0, <6.2.5
>=6.3.0, <6.3.5
>=6.4.0, <6.4.5
>=6.5.0, <6.5.5
5.9.10
6.0.9
6.1.7
6.2.5
6.3.5
6.4.5
6.5.5

Affected products

  • WordPress Foundation WordPress

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.