{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-100175 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-100175 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100175 is a medium-severity vulnerability in wayneallen-1 Postie, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-100175 and fix it if it is affected.\n\nWhat it is: CVE-2026-100175 is a medium-severity vulnerability in wayneallen-1 Postie, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-100175 in the wild and no public exploit code.\n\nAffected product: wayneallen-1 Postie. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-100175/ (Markdown: https://insights.sbomify.com/CVE-2026-100175/index.md)","id":"CVE-2026-100175","markdown":"https://insights.sbomify.com/CVE-2026-100175/index.md","name":"CVE-2026-100175","record":{"aliases":["GHSA-37r8-fq3j-qq4r"],"analysis":null,"analysis_generated_by":null,"assigner":"Wordfence","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Postie \u003c= 1.9.87 - Unauthenticated Stored Cross-Site Scripting via Email Body URL Autolink","id":"CVE-2026-100175","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"Stored Cross-Site Scripting (XSS) in AIL Framework Username Timeline Tooltip","id":"CVE-2026-100176"},"packages":[],"prev":{"headline":"Stored Cross-Site Scripting (XSS) in AIL Framework Tag Selector via Unescaped Tag Names","id":"CVE-2026-100174"},"products":["Postie"],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["wayneallen-1"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-100175/"}