CVE-2024-11141: The Sailthru Triggermail WordPress plugin through 1.1 does not sanitise and escape some of its settings and is

Q: How do I fix CVE-2024-11141?

sailthru triggermail: upgrade to newer than 1.1. Exact commands for each OS are on this page.

Q: Is CVE-2024-11141 being exploited?

CVE-2024-11141 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-11141 affect?

CVE-2024-11141 affects sailthru triggermail. Severity is medium (CVSS 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_htm

Q: How urgent is CVE-2024-11141?

Priority 28/100. Public exploit reference

Routine

MEDIUM 6.1UPGRADE

CVE-2024-11141 is a medium-severity flaw (CVSS 6.1) affecting sailthru triggermail. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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).

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 93%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-05-15
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: jontasc

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-05-15 20:15 UTCPublished CVE record published
2026-06-17 06:57 UTCUpdated Record last modified

jontasc sailthru triggermail UPGRADE

Affected: <= 1.1

Fixed in: newer than 1.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy sailthru-triggermail || rpm -q sailthru-triggermail || sailthru-triggermail --version

2. UPGRADE to newer than 1.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade sailthru-triggermail

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade sailthru-triggermail

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-11141?

sailthru triggermail: upgrade to newer than 1.1. Exact commands for each OS are on this page.

Is CVE-2024-11141 being exploited?

CVE-2024-11141 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-11141 affect?

CVE-2024-11141 affects sailthru triggermail. Severity is medium (CVSS 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_htm

How urgent is CVE-2024-11141?

Priority 28/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs