CVE-2023-5561 | WordPress < 6.3.2 - Unauthenticated Post Author Email Disclosure

Exp

WordPress does not properly restrict which user fields are searchable via the REST API, allowing unauthenticated attackers to discern the email addresses of users who have published public posts on an affected website via an Oracle style attack

Published: 2023-10-16 Last update: 2025-04-23 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-5561 is rated High Exploit Risk (70.7/100): CVSS Medium severity, with high exploitation likelihood (EPSS 53.02%, 98th percentile). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2023-5561

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2023-5561

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-04 52.75% 53.02% +0.28%
2 2026-03-01 53.02% 52.75% -0.28%
3 2026-02-04 — 53.02% —

Full EPSS history (67 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-5561

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 [email protected]
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2023-5561

OS Trackers for CVE-2023-5561

vendor priority summary link
debian not yet assigned CVE-2023-5561 not yet assigned priority: Debian including 1 source packages (wordpress), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2023-5561
ubuntu medium CVE-2023-5561 medium priority: Ubuntu including 1 source packages (wordpress), 12 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 5, ignored 3, not-affected 3, released 1. https://ubuntu.com/security/CVE-2023-5561

Affected software / configurations for CVE-2023-5561

Vendor Product Version Raw CPE
wordpress wordpress >= 4.7, < 4.7.27 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 4.8, < 4.8.23 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 4.9, < 4.9.24 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.0, < 5.0.20 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.1, < 5.1.17 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.2, < 5.2.19 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.3, < 5.3.16 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.4, < 5.4.14 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.5, < 5.5.13 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.6, < 5.6.12 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.7, < 5.7.10 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.8, < 5.8.8 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.9, < 5.9.8 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 6.0, < 6.0.6 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 6.1, < 6.1.4 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 6.2, < 6.2.3 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 6.3, < 6.3.2 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*

References for CVE-2023-5561

cvelogic Threat Intelligence