WordPress Core < 6.0.3 - Information Disclosure (Email Address)
Strategic Overview
- Status
- Patched in 3.7.40
- Affected Core
- WordPress 6.0
- Affected Version
3.6.1 – 6.0.2 · 25 branches- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2022-43504
At a glance
CVE-2022-43504 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WordPress 6.0 WordPress release line, affecting 3.6.1 – 6.0.2 · 25 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 3.7.40; sites on affected versions should update now. Disclosed October 2022, reported by Toshitsugu Yoneyama of Mitsui Bussan Secure Directions, Inc. via JPCERT.
Vulnerability Overview
WordPress Core is vulnerable to Information Disclosure of in versions up to 6.0.3. When the post by email functionality is enabled, it may log post author's email addresses in a way that may be publicly accessible. This could make it possible for attackers to steal post author's email addresses and use that for further attacks.
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
Reaching this weakness in WordPress 6.0 3.6.1 – 6.0.2 · 25 branches 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.0 the fix is 3.7.40: builds 3.6.1 – 6.0.2 · 25 branches are affected, anything from 3.7.40 onward is not.
Remediation
Update to one of the following versions, or a newer patched version: 3.7.40, 3.8.40, 3.9.38, 4.0.37, 4.1.37, 4.2.34, 4.3.30, 4.4.29, 4.5.28, 4.6.25, 4.7.25, 4.8.21, 4.9.22, 5.0.18, 5.1.15, 5.2.17, 5.3.14, 5.4.12, 5.5.11, 5.6.10, 5.7.8, 5.8.6, 5.9.5, 6.0.3
How does WordSec protect against this?
The fix is the thing that ends this: updating to 3.7.40 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.0
- 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