Your WordPress Site Just Leaked Its Keys: AI Makes That Exploit Even Worse

You wouldn’t leave a spare key under the doormat in 2026. And yet, over 100,000 WordPress sites just did exactly that.

On March 30, Wordfence disclosed CVE-2026-4020 in Gravity SMTP, a plugin used to route email safely through WordPress. The flaw lets unauthenticated attackers pull configuration data, API keys, secrets, and OAuth tokens straight out of your site. The patch shipped months ago. Active exploitation is happening right now, confirmed by Wordfence, CrowdSec, and the WIU Cybersecurity Center on June 20, 2026.

That means your email provider token, your SMTP credentials, and possibly other plugin secrets are sitting in an attacker’s spreadsheet.

Why AI Changes the Stakes

Key theft used to mean manual phishing emails or slow credential-stuffing. In 2026, those stolen keys are weaponised at scale using AI.

Here is the math that should worry you: World Economic Forum data released at Davos 2026 found 87 percent of global executives now call AI-related vulnerabilities the fastest-growing cyber risk. Enterprises scaled generative AI across workflows 18 to 24 months faster than their security governance could catch up. Only one in three organisations deployed AI tools with no prior security validation.

Right now, an attacker with a fresh batch of API keys can use AI to craft personalised, context-aware phishing faster than a human operations team can respond. A leaked Gravity SMTP token gives them a legitimate-looking sender. A generative AI tool writes the follow-up email in perfect context. The victim clicks. That is not hypothetical. That is the current threat model.

Three Things to Do Today

First, check whether Gravity SMTP is active in your WordPress plugins. If it is, confirm it is patched. Wordfence said the patch is available; update immediately.

Second, rotate any API keys or OAuth tokens that pass through your WordPress email stack. Do not reuse the old ones anywhere else.

Third, audit which of your connected services actually need WordPress email routing. The more services tied to one plugin, the larger the blast radius if it leaks. If you do not need SMTP integration, remove it.

For site owners, plugin updates should happen the same day they are released. If you are running a business site, let that sink in: a single patched plugin is the difference between a clean audit and a data breach claim under your insurer’s cyber policy.

Enterprise AI deployment is now 18 to 24 months ahead of mature AI security governance. Attackers are exploiting that gap with stolen credentials and AI-generated social engineering. That is where we are right now.

Related Reading

Subscribe

Related articles

AI Agents, Copilot and the New Security Risk: When Helpful Becomes Dangerous

AI agents are moving from passive assistants to active participants in the workplace. When connected to email, files, terminals and cloud services, they introduce a new class of security risk that requires governance, not just policies.

North Korean Hackers Poisoned 144 AI npm Packages: Check Your Dependencies Now

A North Korean state-sponsored group backdoored 144 Mastra AI npm packages with a malicious dayjs typosquat. The postinstall hook ran automatically on npm install, exposing developer machines and CI/CD pipelines to credential theft and full system compromise.

Your AI Agents Are Now a Security Risk: What the Last 48 Hours Proved

AutoJack, FortiBleed, and evolved LLMjacking show AI agents and self-hosted inference are now live attack surfaces. Here's what enterprises need to patch this week.

The Rise of Autonomous AI Voice Agents: What It Means When the Machine Calls for You

AI voice agents have evolved into autonomous systems that negotiate bills, cancel subscriptions, and appeal insurance denials on your behalf. Here is how they work and what it means for consumers.

24 Billion Records Exposed: The Credential Leak That Changes Everything

Cybernews researchers have discovered an Elasticsearch database containing 24 billion exposed credentials, including usernames, passwords, and login URLs in plaintext. Here is what it means and how to protect yourself.