CVE-2026-100175
Received Received - Intake

Stored XSS in Postie WordPress Plugin via Email Body URL Autolink

Publication date: 2026-10-28

Last updated on: 2026-10-28

Assigner: Wordfence

Description
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 arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is possible because the ?postie=get-mail endpoint is reachable by unauthenticated users with no capability check, and the email processing path removes WordPress's kses output filters before saving raw markup, allowing the unescaped href attribute value to be stored as post content.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-28
Last Modified
2026-10-28
Generated
2026-10-28
AI Q&A
2026-10-28
EPSS Evaluated
N/A
NVD
CVE-2026-100175
EUVD
EUVD-2026-111751

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
wayneallen-1 Postie 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The Postie WordPress plugin up to version 1.9.87 has a stored XSS flaw. Unauthenticated attackers can inject malicious scripts via email body URLs. The plugin fails to sanitize input and removes WordPress's output filters before saving raw markup, allowing unescaped malicious code to be stored as post content.

Detection Guidance

Check for the Postie plugin version in WordPress admin. If using version 1.9.87 or lower, the system is vulnerable. Inspect WordPress pages for stored scripts in email body URLs via the ?postie=get-mail endpoint.

Impact Analysis

Attackers can execute arbitrary scripts in a victim's browser when they view an infected page. This could lead to session hijacking, defacement, or theft of sensitive data like cookies or credentials. Users with admin access are particularly at risk if the injected script runs in the WordPress admin interface.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating GDPR's integrity and confidentiality principles. For HIPAA, it may compromise protected health information if exploited on healthcare-related sites. Organizations must address it to maintain compliance with data protection requirements.

Mitigation Strategies
  • Update the Postie plugin to the latest version immediately.
  • Remove or disable the Postie plugin if an update is unavailable.
  • Review WordPress pages for suspicious scripts and remove them.
  • Ensure WordPress core and all plugins are updated to the latest versions.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-100175. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart