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

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

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

Q: Is CVE-2024-4290 being exploited?

CVE-2024-4290 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-4290 affect?

CVE-2024-4290 affects sailthru triggermail. Severity is high (CVSS 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 capab

Q: How urgent is CVE-2024-4290?

Priority 38/100. High severity; Public exploit reference

Routine

HIGH 7.1UPGRADE

CVE-2024-4290 is a high-severity flaw (CVSS 7.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, 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)

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.4% (top 67%)
CISA exploited list	No
Weakness	CWE-79
Published	2024-05-21
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

2024-05-21 06:15 UTCPublished CVE record published
2026-06-17 08:01 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-4290?

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

Is CVE-2024-4290 being exploited?

CVE-2024-4290 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-4290 affect?

CVE-2024-4290 affects sailthru triggermail. Severity is high (CVSS 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 capab

How urgent is CVE-2024-4290?

Priority 38/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-4289 MEDIUM 6.1 UPGRADE The Sailthru Triggermail WordPress plugin through 1.1 does not sanitise and escape various parameters before o
CVE-2024-11141 MEDIUM 6.1 UPGRADE The Sailthru Triggermail WordPress plugin through 1.1 does not sanitise and escape some of its settings and is

References

← Back to latest CVEs