Unauthenticated post publication via forged email sender
Published Jan 1, 2020 · Updated Aug 5, 2024
Authentication bypass in the Postie plugin 1.9.40 for WordPress allows remote attackers to publish posts via forged email sender data. Authorized Addresses trusts the message's From header as proof of an approved sender without authenticating the message source. Exploitation requires knowledge of the secret Postie mailbox and an authorized sender address, plus a mail server that accepts spoofed headers; success creates an unauthorized WordPress post.
Summary
What happened
Authentication bypass in the Postie plugin 1.9.40 for WordPress allows remote attackers to publish posts via forged email sender data. Authorized Addresses trusts the message's From header as proof of an approved sender without authenticating the message source. Exploitation requires knowledge of the secret Postie mailbox and an authorized sender address, plus a mail server that accepts spoofed headers; success creates an unauthorized WordPress post.
The record
- CVE
- CVE-2019-20203
- Published
- Jan 1, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-290, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 1, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Exploiting Postie WordPress Plugin PoC 1proof of concept · demonstrated
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