MailPoet – Newsletters, Email Marketing, and Automation 5.30.0-5.33.0 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 5.33.1
- Affected Plugin
- MailPoet – Newsletters, Email Marketing, and Automation
- Affected Version
5.30.0 – 5.33.0- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-57626
At a glance
CVE-2026-57626 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the MailPoet WordPress plugin, affecting versions 5.30.0 – 5.33.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.33.1; sites on affected versions should update now. Disclosed July 2026, reported by Nguyen Ba Khanh.
Vulnerability Overview
The MailPoet – Newsletters, Email Marketing, and Automation plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to 5.30.0-5.33.0. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in MailPoet 5.30.0 – 5.33.0 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For MailPoet the fix is 5.33.1: builds 5.30.0 – 5.33.0 are affected, anything from 5.33.1 onward is not.
Remediation
Update to version 5.33.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to MailPoet: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: MailPoet 5.33.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in MailPoet – Newsletters, Email Marketing, and Automation
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C