The Postie plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Email Body URL Autolink in all versions up to, and including, 1.9.87 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitra...
Product
wordpress postie vulnerabilities
6 published CVES affecting wordpress postie, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 0
- High
- 0
- Medium
- 6
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress postie CVEs
Newest publication first
-
MediumCVSS 5.4 EPSS 0.33%
-
CVE-2025-63020 WordPress Postie plugin <= 1.9.73 - Cross Site Scripting (XSS) vulnerability
PublishedMediumCVSS 6.5 EPSS 0.16%Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Wayne Allen Postie postie allows Stored XSS.This issue affects Postie: from n/a through <= 1.9.73.
-
MediumCVSS 4.8 EPSS 0.18%
The Postie WordPress plugin before 1.9.71 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)...
-
MediumCVSS 5.4 EPSS 3.4% Public exploit
The Postie plugin 1.9.40 for WordPress allows XSS, as demonstrated by a certain payload with jaVasCript:/* at the beginning and a crafted SVG element.
-
MediumCVSS 5.3 EPSS 2.1%
The Authorized Addresses feature in the Postie plugin 1.9.40 for WordPress allows remote attackers to publish posts by spoofing the From information of an email message.
-
MediumCVSS 4.3 EPSS 3.7% Public exploit
Cross-site scripting (XSS) vulnerability in the Postie plugin 1.4.3, and possibly before 1.5.15, for WordPress allows remote attackers to inject arbitrary web script or HTML via the From field of an email.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.