CVE-2023-5561 json
WordPress < 6.3.2 - Unauthenticated Post Author Email Disclosure
published 3y ago modified 2mo ago also BIT-wordpress-2023-5561 , BIT-wordpress-multisite-2023-5561 , EUVD-2023-57861
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.3%
- EPSS 4.3% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- bitnami wordpress 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.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 WordPress 4.7.27, 4.8.23, 4.9.24, 5.0.20, 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-5561
Is CVE-2023-5561 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
4.34% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-15).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/19380917-4c27-4095-abf1-eba6f913b441 referenced PoC, tagged "exploit" by a source, unverified
- wpscan.com https://wpscan.com/blog/email-leak-oracle-vulnerability-addressed-in-wordpress-6-3-2/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| 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 | >=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.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.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.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 WordPress
Classification
- Technology feeds
References
-
wpscan.com
/vulnerability/19380917-4c27-4095-abf1-eba6f913b441
exploit, vdb-entry, technical-description, third-party-advisory, advisory
-
wpscan.com
/blog/email-leak-oracle-vulnerability-addressed-in-wordpress-6-3-2/
technical-description, exploit, third-party-advisory, advisory
-
lists.debian.org
/debian-lts-announce/2023/11/msg00014.html
web
-
nvd.nist.gov
/vuln/detail/CVE-2023-5561
web
Sources
- CVE List CVE-2023-5561
- NVD CVE-2023-5561
- OSV BIT-wordpress-2023-5561
- OSV BIT-wordpress-multisite-2023-5561
Fencer Intel 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.