Skip to content
Fencer Vulns
medium 5.3

CVE-2023-5692 json

WordPress Core <= 6.4.3 - Sensitive Information Exposure via redirect_guess_404_permalink

published 2024-04-05 2 y ago modified 2026-06-17 4 mo ago also BIT-wordpress-2023-5692 , BIT-wordpress-multisite-2023-5692 , EUVD-2023-57979

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

Summary

WordPress Core is vulnerable to Sensitive Information Exposure in versions up to, and including, 6.4.3 via the redirect_guess_404_permalink function. This can allow unauthenticated attackers to expose the slug of a custom post whose 'publicly_queryable' post status has been set to 'false'.

Patch / fix

  • bitnami wordpress 6.5.0
  • bitnami wordpress-multisite 6.5.0
  • wordpress wordpress 6.5
  • johnpbloch wordpress-core 6.5
  • wordpress Debian 14, Debian 13 6.5+dfsg1-1

debian advisories DEBIAN-CVE-2023-5692

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-5692 updated cvss 5.3

wordpress: potential exposure of custom post slugs whose 'publicly_queryable' post status has been set to 'false'

  • 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.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
bitnami wordpress
<6.5.0
6.5.0
bitnami wordpress-multisite
<6.5.0
6.5.0

Affected products

  • WordPress Foundation 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.

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