CVE-2026-78003Mailgun for WordPress <= 2.2.0 - Unauthenticated Server-Side Request Forgery (SSRF) via 'addresses' Array Keys
- 9.8CriticalCVSS base score
- 0.79%Exploitation in 30 daysEPSS · top 43% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
The Mailgun for WordPress plugin for WordPress is vulnerable to Server-Side Request Forgery (SSRF) via path traversal in versions up to and including 2.2.0. This is due to insufficient input validation in the add_list() function, which accepts user-controlled array keys from $_POST['addresses'], passes them through sanitize_text_field(). This makes it possible for unauthenticated attackers to make authenticated POST requests to any Mailgun API endpoint using the WordPress site's API key, including creating inbound email-forwarding routes that can intercept password reset emails, leading to administrator account takeover.
Timeline
ID reserved
By Wordfence
- 1 day later
· 1 day later
Published
- 3 days later
· 3 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| WordfenceCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Deferred | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.79% · top 43% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
mailgun · Mailgun for WordPress
- affected ≤ 2.2.0
References
References9
- https://www.wordfence.com/threat-intel/vulnerabilities/id/110e888d-69fc-4682-b908-2b62288c5227?source=cve (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/mailgun/trunk/mailgun.php#L557 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/mailgun/trunk/mailgun.php#L259 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/mailgun/tags/2.1.10/mailgun.php#L259 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/mailgun/trunk/mailgun.php#L323 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/mailgun/tags/2.1.10/mailgun.php#L323 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/mailgun/trunk/mailgun.php#L331 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/mailgun/tags/2.1.10/mailgun.php#L331 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/mailgun/tags/2.1.10/mailgun.php#L557 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-64242 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-78003)Record last updated .