Loading vulnerability…
CVE-2026-78003 is a server-side request forgery vulnerability in the Mailgun for WordPress plugin affecting versions up to and including 2.2.0. The flaw is caused by insufficient input validation in the add_list() function, which accepts user-controlled array keys from POST-supplied address data and processes them with sanitize_text_field(), allowing path traversal into Mailgun API request construction. As a result, an unauthenticated attacker can cause the WordPress site to issue authenticated POST requests to arbitrary Mailgun API endpoints using the site’s configured Mailgun API key. This can be abused to create inbound email-forwarding routes and redirect sensitive mail flows, including password reset messages, creating a path to WordPress administrator account takeover.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.