Active Exploitation of Gravity SMTP Flaw Exposes WordPress Email Credentials
Attackers are actively exploiting CVE-2026-4020 in the RocketGenius Gravity SMTP WordPress plugin to extract sensitive configuration data and live email-service credentials from vulnerable sites. The flaw affects versions 2.1.4 and earlier and stems from an unauthenticated REST API endpoint, /wp-json/gravitysmtp/v1/tests/mock-data, whose permission check always returns true; when queried with page=gravitysmtp-settings, it can return a detailed JSON system report containing environment data, API keys, secrets, and OAuth tokens tied to providers including Amazon SES, Google, Mailjet, Resend, and Zoho.
The plugin is installed on roughly 100,000 WordPress sites, raising the risk of credential theft and abuse of legitimate outbound email infrastructure for spam, phishing, or follow-on compromise. Wordfence said it blocked more than 17 million exploitation attempts, including a spike of over 4 million in a single day, while CrowdSec observed at least 412 attacking IPs during earlier scanning and attack activity. RocketGenius released a fix in Gravity SMTP 2.1.5, and defenders are being urged to update immediately, rotate any potentially exposed credentials, and review logs for suspicious requests to the vulnerable endpoint.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
6 events from the most recent confirmed update back to the earliest known activity.
Wordfence publishes IOCs for Gravity SMTP exploitation
Wordfence identified requests to '/wp-json/gravitysmtp/v1/tests/mock-data', especially with the '?page=gravitysmtp-settings' parameter, as indicators of compromise for CVE-2026-4020 exploitation. It also advised administrators to block prolific source IPs and update Gravity SMTP immediately.
CrowdSec observed 412 attacking IPs targeting the flaw
CrowdSec observed at least 412 attacking IPs exploiting or probing CVE-2026-4020 during a late-May to early-June activity window, indicating active malicious interest in the vulnerability.
Researchers report widespread active exploitation in the wild
Security reporting stated that CVE-2026-4020 was under active exploitation against Gravity SMTP installations, with Wordfence blocking more than 17 million exploit attempts overall.
Wordfence saw a major spike in exploitation attempts
Wordfence reported a major spike in blocked exploit attempts against CVE-2026-4020 on June 7, with more than 4 million attempts observed that day as part of a broader June 7-11 surge.
Public disclosure of CVE-2026-4020
Public disclosure of the Gravity SMTP vulnerability followed after the fix release, identifying an unauthenticated REST API endpoint that could expose system reports and secrets.
Gravity SMTP 2.1.5 released to fix CVE-2026-4020
RocketGenius released Gravity SMTP version 2.1.5 to address CVE-2026-4020, a sensitive information exposure flaw affecting versions 2.1.4 and earlier.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
4 references tracked. Mallory keeps watching after this page renders.
Hackers Exploit Gravity SMTP WordPress Plugin Bug to Expose API Keys
thehackernews.com
Open sourceHackers exploit info disclosure bug in Gravity SMTP WordPress plugin
bleepingcomputer.com
Open sourceHackers Actively Exploiting WordPress SMTP Plugin With 100,000+ Installs to Access Sensitive Data
cybersecuritynews.com
Open sourceActive Gravity SMTP Vulnerability Exploited in the Wild
securityonline.info
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


