WordPress Core 4.7.0 - 6.3.1 - Sensitive Information Exposure via User Search REST Endpoint
Strategic Overview
- Status
- Patched in 4.7.27
- Affected Core
- WordPress 6.3
- Affected Version
4.7 – 6.3.1 · 17 branches- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2023-5561
At a glance
CVE-2023-5561 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WordPress 6.3 WordPress release line, affecting 4.7 – 6.3.1 · 17 branches. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.7.27; sites on affected versions should update now. Disclosed October 2023, reported by Marc-Alexandre Montpas.
Vulnerability Overview
WordPress Core is vulnerable to Sensitive Information Exposure in versions between 4.7.0 and 6.3.1 via the User REST endpoint. While the search results do not display user email addresses unless the requesting user has the 'list_users' capability, the search is applied to the user_email column. This can allow unauthenticated attackers to brute force or verify the email addresses of users with published posts or pages on the site.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
WordPress 6.3 4.7 – 6.3.1 · 17 branches carries this weakness at list_users, and reaching it takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WordPress 6.3 the fix is 4.7.27: builds 4.7 – 6.3.1 · 17 branches are affected, anything from 4.7.27 onward is not.
Remediation
Update to one of the following versions, or a newer patched version: 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
How does WordSec protect against this?
The fix is the thing that ends this: updating to 4.7.27 is the step that ends it.
- Alerts
External References
Related records
Same weakness class
- 7.5CVE-2018-20151: WordPress Core < 5.0.1 Info Disclosure
CVE-2018-20151 - 7.5CVE-2011-3818: WordPress Core 2.9.2 and 3.0.4 Info Disclosure
CVE-2011-3818 - 7.5CVE-2006-0986: WordPress Core < 2.0.2 Sensitive Information Disclosure
CVE-2006-0986 - 7.3CVE-2005-2110: WordPress Core < 1.5.1.3 Info Disclosure
CVE-2005-2110
Other vulnerabilities in WordPress 6.3
- 9.8CVE-2026-63030: WordPress Core 6.9 - 7.0.1 Remote Code Execution
CVE-2026-63030 - 9.8CVE-2024-31211: WordPress Core 6.4.0 - 6.4.1 RCE POP Chain
CVE-2024-31211 - 9.8WordPress Core < 6.0.3 SQL Injection via WP_Date_Query
- 9.8CVE-2021-29476: WordPress Core < 5.5.3 PHP Object Injection Gadget
CVE-2021-29476 - 9.8CVE-2017-16510: WordPress Core SQL Injection
CVE-2017-16510 - 9.8CVE-2017-14723: WordPress Core < 4.8.2 SQL Injection
CVE-2017-14723 - 9.8CVE-2007-6013: WordPress Core 1.5 - 2.3.1 Authorization Bypass
CVE-2007-6013 - 9.8CVE-2007-6318: WordPress Core < 2.3.2 SQL Injection
CVE-2007-6318
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C