<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: sailthru triggermail</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2024-11141: The Sailthru Triggermail WordPress plugin through 1.1 does not sanitise and escape some of its settings and is</title><link>https://patchthecve.com/cve/CVE-2024-11141.html</link><guid>https://patchthecve.com/cve/CVE-2024-11141.html</guid><pubDate>Wed, 17 Jun 2026 06:57:09 +0000</pubDate><description>MEDIUM 6.1: The Sailthru Triggermail WordPress plugin through 1.1 does not sanitise and escape some of its settings and is missing CSRF protection which could allow subscribers to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).</description></item><item><title>CVE-2024-4290: The Sailthru Triggermail WordPress plugin through 1.1 does not sanitise and escape some of its settings, which</title><link>https://patchthecve.com/cve/CVE-2024-4290.html</link><guid>https://patchthecve.com/cve/CVE-2024-4290.html</guid><pubDate>Wed, 17 Jun 2026 08:01:36 +0000</pubDate><description>HIGH 7.1: The Sailthru Triggermail WordPress plugin through 1.1 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)</description></item><item><title>CVE-2024-4289: The Sailthru Triggermail WordPress plugin through 1.1 does not sanitise and escape various parameters before o</title><link>https://patchthecve.com/cve/CVE-2024-4289.html</link><guid>https://patchthecve.com/cve/CVE-2024-4289.html</guid><pubDate>Wed, 17 Jun 2026 08:01:36 +0000</pubDate><description>MEDIUM 6.1: The Sailthru Triggermail WordPress plugin through 1.1 does not sanitise and escape various parameters before outputting them back in pages and attributes, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin</description></item></channel></rss>