Sailthru Triggermail
sailthru-triggermail · plugin
Known security vulnerabilities for Sailthru Triggermail. Find out in seconds which version runs on your site with WP Lens.
3 known vulnerabilities
3 with no official fix seen · latest May 15, 2025
Before you install
Do not install
- 3 records show no fix in the latest wordpress.org release.
- Last updated Sep 22, 2010: not updated for more than two years.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 1.1 · last updated Sep 22, 2010
Not updated since Sep 22, 2010. A component left without updates for over two years should not be expected to patch new vulnerabilities.
wordpress.org status checked on Nov 5, 2026
Vulnerabilities
- High 7.1
CVE-2024-4290adminno fix seen
Sailthru Triggermail <= 1.1 - Admin+ Stored XSS
- Medium 6.1
CVE-2024-11141subscriber+no fix seen
Sailthru Triggermail < 1.1 - Subscriber+ Stored XSS
- Medium 6.1
CVE-2024-4289adminno fix seen
Sailthru Triggermail <= 1.1 - Reflected XSS
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS). The record lists the latest wordpress.org release (1.1) as affected.