WordPress security by component
Postie
Plugin description
Postie is a WordPress component with 5 published CVE records in this archive. The latest tracked vulnerability was published Dec 31, 2025; the highest CVE/CNA score is 6.5.
Plugin slug:
postieLatest vulnerability
CVE-2025-63020: Postie: Cross-site scripting
Postie is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
| Safe version |
|
||
|---|---|---|---|
| Dec 31, 2025 |
CVE-2025-63020
Postie: Cross-site scripting
Postie is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.5
NVDPending
|
| Sep 29, 2025 |
CVE-2024-5200
Postie: Cross-site scripting
Postie is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE4.8
NVDPending
|
| Jan 02, 2020 |
CVE-2019-20204
Postie: Cross-site scripting
Postie is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE5.4
NVD5.4
|
| Jan 02, 2020 |
CVE-2019-20203
Postie: A security weakness
Postie is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVD5.3
|
| Jun 20, 2014 |
CVE-2012-2580
Postie: Cross-site scripting
Postie is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE4.3
NVD4.3
|