Skip to content
Fencer Vulns
medium 4.3

CVE-2023-39999 json

WordPress < 6.3.2 is vulnerable to Broken Access Control

published 2023-10-13 3 y ago modified 2026-10-05 34 d ago also BIT-wordpress-2023-39999 , BIT-wordpress-multisite-2023-39999 , EUVD-2023-43692

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

Summary

Exposure of Sensitive Information to an Unauthorized Actor in WordPress from 6.3 through 6.3.1, from 6.2 through 6.2.2, from 6.1 through 6.13, from 6.0 through 6.0.5, from 5.9 through 5.9.7, from 5.8 through 5.8.7, from 5.7 through 5.7.9, from 5.6 through 5.6.11, from 5.5 through 5.5.12, from 5.4 through 5.4.13, from 5.3 through 5.3.15, from 5.2 through 5.2.18, from 5.1 through 5.1.16, from 5.0 through 5.0.19, from 4.9 through 4.9.23, from 4.8 through 4.8.22, from 4.7 through 4.7.26, from 4.6 through 4.6.26, from 4.5 through 4.5.29, from 4.4 through 4.4.30, from 4.3 through 4.3.31, from 4.2 through 4.2.35, from 4.1 through 4.1.38.

Patch / fix

  • bitnami wordpress 4.1.39, 4.2.36, 4.3.32, 4.4.31, 4.5.30, 4.6.27, 4.7.27, 4.8.23, 4.9.24, 5.0.20, 5.1.17, 5.2.19, 5.3.16, 5.4.14, 5.5.13, 5.6.12, 5.7.10, 5.8.8, 5.9.8, 6.0.6, 6.1.4, 6.2.3, 6.3.2
  • bitnami wordpress-multisite 4.1.39, 4.2.36, 4.3.32, 4.4.31, 4.5.30, 4.6.27, 4.7.27, 4.8.23, 4.9.24, 5.0.20, 5.1.17, 5.2.19, 5.3.16, 5.4.14, 5.5.13, 5.6.12, 5.7.10, 5.8.8, 5.9.8, 6.0.6, 6.1.4, 6.2.3, 6.3.2
  • WordPress.org WordPress 4.4.31, 4.5.30, 4.6.27, 4.7.27, 4.8.23, 4.9.24, 5.0.20, 5.1.17, 5.2.19, 5.3.16, 5.4.14, 5.5.13, 5.6.12, 5.7.10, 5.8.8, 5.9.8, 6.0.6, 6.1.4, 6.2.3, 6.3.2
  • wordpress Debian 12 6.1.6+dfsg1-0+deb12u1
  • wordpress Debian 14, Debian 13 6.3.2+dfsg1-1

debian advisories DEBIAN-CVE-2023-39999

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-2023-39999 updated

wordpress: potential sensitive information exposure from unauthorized actors

  • 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

Exploit prediction

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

Exploits and checks

  • patchstack.com https://patchstack.com/articles/wordpress-core-6-3-2-security-update-technical-advisory?_s_id=cve referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected packages

ecosystem package affected fixed in
bitnami wordpress
>=4.1.0, <4.1.39
>=4.2.0, <4.2.36
>=4.3.0, <4.3.32
>=4.4.0, <4.4.31
>=4.5.0, <4.5.30
>=4.6.0, <4.6.27
>=4.7.0, <4.7.27
>=4.8.0, <4.8.23
>=4.9.0, <4.9.24
>=5.0.0, <5.0.20
>=5.1.0, <5.1.17
>=5.2.0, <5.2.19
>=5.3.0, <5.3.16
>=5.4.0, <5.4.14
>=5.5.0, <5.5.13
>=5.6.0, <5.6.12
>=5.7.0, <5.7.10
>=5.8.0, <5.8.8
>=5.9.0, <5.9.8
>=6.0.0, <6.0.6
>=6.1.0, <6.1.4
>=6.2.0, <6.2.3
>=6.3.0, <6.3.2
4.1.39
4.2.36
4.3.32
4.4.31
4.5.30
4.6.27
4.7.27
4.8.23
4.9.24
5.0.20
5.1.17
5.2.19
5.3.16
5.4.14
5.5.13
5.6.12
5.7.10
5.8.8
5.9.8
6.0.6
6.1.4
6.2.3
6.3.2
bitnami wordpress-multisite
>=4.1.0, <4.1.39
>=4.2.0, <4.2.36
>=4.3.0, <4.3.32
>=4.4.0, <4.4.31
>=4.5.0, <4.5.30
>=4.6.0, <4.6.27
>=4.7.0, <4.7.27
>=4.8.0, <4.8.23
>=4.9.0, <4.9.24
>=5.0.0, <5.0.20
>=5.1.0, <5.1.17
>=5.2.0, <5.2.19
>=5.3.0, <5.3.16
>=5.4.0, <5.4.14
>=5.5.0, <5.5.13
>=5.6.0, <5.6.12
>=5.7.0, <5.7.10
>=5.8.0, <5.8.8
>=5.9.0, <5.9.8
>=6.0.0, <6.0.6
>=6.1.0, <6.1.4
>=6.2.0, <6.2.3
>=6.3.0, <6.3.2
4.1.39
4.2.36
4.3.32
4.4.31
4.5.30
4.6.27
4.7.27
4.8.23
4.9.24
5.0.20
5.1.17
5.2.19
5.3.16
5.4.14
5.5.13
5.6.12
5.7.10
5.8.8
5.9.8
6.0.6
6.1.4
6.2.3
6.3.2

Affected products

  • WordPress.org WordPress

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
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.