Live › vulnerability › CVE-2026-100175
Go to dashboardThe Postie plugin for WordPress, up to and including version 1.9.87, lets an unauthenticated attacker send email that gets saved as page content with unsanitized markup. When a logged-in user opens the injected page, the attacker's script runs in their browser.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 07:31 UTC. All times on this page are UTC.
Sites running the Postie plugin at version or earlier that accept mail through its email-to-post feature are exposed. Sites without Postie, or with a newer version, are not affected. The sources do not say whether non-default configuration is required.
1.9.87No product ranges from the sources yet.
wp plugin get postie --field=version?postie=get-mail responds on the site1.9.87Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-100175")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.