Skip to content
Web

CVE-2026-78003

9.8
Critical
EPSS 0.87%Patch availableAug 22, 2026

Unauthenticated SSRF in Mailgun WordPress plugin enables API key abuse and admin takeover.

common questions

Is CVE-2026-78003 being exploited?

Not confirmed. CVE-2026-78003 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.87% probability of exploitation in the next 30 days.

How severe is CVE-2026-78003?

CVE-2026-78003 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-78003?

Yes. A fix has been recorded for CVE-2026-78003. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-78003 affect?

CVE-2026-78003 affects Mailgun for WordPress plugin <=2.2.0, WordPress sites using Mailgun plugin, Mailgun API (abused via site API key). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-78003?

Update Mailgun plugin to patched version and rotate Mailgun API keys.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Mailgun for WordPress plugin <=2.2.0WordPress sites using Mailgun pluginMailgun API (abused via site API key)
impact

Unauthenticated SSRF allows attackers to use the site's Mailgun API key to create forwarding routes, intercept password resets, and hijack admin accounts.

action required

Immediate action required

affected versions
mailgun Mailgun for WordPress
  • affected<= 2.2.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free