Stored script execution via unsanitized emailed posts
Published Dec 5, 2022 · Updated Apr 24, 2025
Stored XSS in WordPress before 6.0.3 allows remote attackers to run arbitrary script in a visitor's browser through Post by Email. wp-mail.php processed emailed post content under the current web user, allowing privileged sessions to bypass KSES filtering before storage. Exploitation requires Post by Email to be configured and a user to view the injected post, where the script runs within the site's browser origin.
Summary
What happened
Stored XSS in WordPress before 6.0.3 allows remote attackers to run arbitrary script in a visitor's browser through Post by Email. wp-mail.php processed emailed post content under the current web user, allowing privileged sessions to bypass KSES filtering before storage. Exploitation requires Post by Email to be configured and a user to view the injected post, where the script runs within the site's browser origin.
The record
- CVE
- CVE-2022-43500
- Published
- Dec 5, 2022
- Updated
- Apr 24, 2025
- Vendor
- WordPress.org
- Product
- WordPress
- Classifications
- CWE-79, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 5, 2022CVE publishedPublication date reported by the CVE source.
- 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.
- Affected versionversion=versions prior to 6.0.3
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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