CVE-2022-43504Network attack vector

Email-address disclosure via post-by-email output

Published Dec 5, 2022 · Updated Apr 24, 2025

Improper authentication in WordPress before 6.0.3 allows remote attackers to read post authors' email addresses through wp-mail.php. When Post by Email is configured, an unauthenticated request causes wp-mail.php to print the sanitized sender address before matching it to a user. Exposure is limited to the sender address of a queued message processed by the endpoint, with no reported ability to alter data or interrupt service.

CVSS severity5.3
Medium
EPSS probability1.44%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper authentication in WordPress before 6.0.3 allows remote attackers to read post authors' email addresses through wp-mail.php. When Post by Email is configured, an unauthenticated request causes wp-mail.php to print the sanitized sender address before matching it to a user. Exposure is limited to the sender address of a queued message processed by the endpoint, with no reported ability to alter data or interrupt service.

The record

CVE
CVE-2022-43504
Published
Dec 5, 2022
Updated
Apr 24, 2025
Vendor
WordPress.org
Product
WordPress
Classifications
CWE-287, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Dec 5, 2022CVE publishedPublication date reported by the CVE source.
  2. Apr 24, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=versions prior to 6.0.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

WordPress.org · WordPressversion=versions prior to 6.0.3

Published CVSS scores

5.0JPCERT/CC and IPAAV:N/AC:L/Au:N/C:P/I:N/A:N
5.3CISA ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
5.3JPCERT/CC and IPACVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-287Improper Authentication
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo