Mailgun for WordPress <= 2.2.0 - Missing Authorization to Unauthenticated Arbitrary Mailgun List Subscription
Strategic Overview
- Status
- Patched in 2.2.1
- Affected Plugin
- Mailgun for WordPress
- Affected Version
<= 2.2.0- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-14834
At a glance
CVE-2026-14834 is a medium-severity Missing Authorization vulnerability in the Mailgun for WordPress WordPress plugin, affecting versions <= 2.2.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.2.1; sites on affected versions should update now. Disclosed July 2026, reported by Pedro Pinho.
Vulnerability Overview
The Mailgun for WordPress plugin for WordPress is vulnerable to unauthorized access in versions up to, and including, 2.2.0. This is due to missing nonce verification and lack of server-side validation of submitted list addresses against configured lists in the add_list() function. This makes it possible for unauthenticated attackers to subscribe arbitrary email addresses to any Mailgun mailing list configured on the site without authentication.
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, and no interaction from a victim user.
CWE-862: Missing Authorization
Mailgun for WordPress <= 2.2.0 carries this weakness at add_list(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Mailgun for WordPress the fix is 2.2.1: builds <= 2.2.0 are affected, anything from 2.2.1 onward is not.
Remediation
Update to version 2.2.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Mailgun for WordPress 2.2.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Mailgun for WordPress
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C