HomeWordPress vulnerabilitiesPostie
Postie vulnerabilities
Postie has 4 known vulnerabilities in this database. The most recent published record is dated 29 Sep 2025.
- Known vulnerabilities
- 4
- Active installs
- 10,000+
- Latest version
- 1.9.87
- Last updated
- 24 Sep 2026
- Most recent
- 29 Sep 2025
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2024-5200 | Medium 4.8 | Before 1.9.71 | Fixed in 1.9.71 | 29 Sep 2025 |
| Cross-site scripting (XSS) CVE-2019-20204 | Medium 5.4 | Up to 1.9.40 | Fixed in a later version (latest 1.9.87) | 2 Jan 2020 |
| Security weakness CVE-2019-20203 | Medium 5.3 | Up to 1.9.40 | Fixed in a later version (latest 1.9.87) | 2 Jan 2020 |
| Cross-site scripting (XSS) CVE-2012-2580 | Not scored | Up to 1.5.14 | Fixed in a later version (latest 1.9.87) | 20 Jun 2014 |
Read the published descriptions
- CVE-2024-5200, 29 Sep 2025
- 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). CVE record
- CVE-2019-20204, 2 Jan 2020
- 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. CVE record
- CVE-2019-20203, 2 Jan 2020
- 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. CVE record
- CVE-2012-2580, 20 Jun 2014
- 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. CVE record
What to do if you run Postie
If you run Postie, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Postie vulnerabilities
Free. We email you when a new vulnerability is published for Postie, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.