On August 28, 2026, Sybre Waaijer — the developer behind The SEO Framework — posted a thread on X that lit the WordPress ecosystem on fire. Rank Math, the SEO plugin active on over 4 million sites, had shipped an update that silently created WordPress Application Passwords with administrator-level permissions. The trigger? A user clicking on the "Help & Support" section inside the plugin. No consent dialog. No warning. No opt-in checkbox.

The credentials were generated automatically, sent to group.one's servers (Rank Math's parent company, which also owns WP Rocket), and labeled "WAP – Rank Math Support Agent" in the user's profile. The password did not expire. Closing the Help tab did not revoke it. There was no toggle to disable it. If the user who clicked Help happened to be an administrator — which, on most WordPress sites, is the default user — the AI support agent inherited full admin-level access.

How it actually worked

The mechanism was straightforward, which is part of what made it alarming. WordPress Application Passwords are a legitimate core feature. They let external applications authenticate with your site using revocable, per-application credentials instead of your main password. Plugins can generate them. The WordPress documentation even includes guidelines for how to do it properly — with an authorization screen that identifies the requesting application, shows the user what permissions are being requested, and requires explicit approval before the password is handed over.

Rank Math skipped all of that. According to Waaijer's analysis of the code in vendor/groupone/wap-client/includes/class-app-password-manager.php, the Application Password was created and transmitted to group.one's servers before the Terms & Conditions checkbox even appeared on screen. The transfer started before any consent UI was visible.

The stated purpose was read-only access for an AI support agent that could answer questions by understanding the context of your specific site. Rank Math later confirmed the agent could not modify the site and inherited only the current user's permissions rather than escalating to higher privileges. The credentials were encrypted and, according to Rank Math, not persisted on their servers.

But none of that matters if the user never agreed to the connection in the first place.

The backlash was immediate and brutal

The WordPress.org support forum had a large thread about the issue. Rank Math deleted it. Users on X reported moving their sites away from Rank Math entirely. The anger was not just about the security implications — it was about trust. A plugin with 4 million active installations silently creating admin credentials is the kind of thing that makes site owners question every plugin on their server.

Roger Montti at Search Engine Journal noted that Rank Math did not make their list of recommended plugins, partly because of a vulnerability history: seven in 2024, four in 2025, and three so far in 2026, including an Unauthenticated Stored Cross-Site Scripting vulnerability. This incident did not help.

Rank Math's response

On August 31, Rank Math published a blog post acknowledging the failure. They paused the Support Agent feature and admitted the consent process was not explicit enough. Their post stated: "When an AI agent is being given permission to create an application password, you should be told clearly and directly what is happening and what you're allowing."

They also revealed that the Support Agent was the first piece of a larger plan to deploy agentic AI inside Rank Math — AI agents that could take actions on your site on your behalf, subject to granted permissions. The support agent was supposed to be the read-only onboarding step for that vision.

Rank Math says the feature will return with a redesigned access-request flow that explains in plain language what permissions are being requested before any credentials are created.

What you should do right now

If you use Rank Math and have ever opened the Help & Support section while connected to a rankmath.com account, check your Application Passwords immediately.

Go to WP Admin → Users → Profile → Application Passwords. Look for anything starting with "WAP –". Revoke it. It takes ten seconds and there is no reason to leave an uninvited credential sitting on your site.

While you are there, review all Application Passwords on every administrator account. If you see anything you do not recognize, revoke it. Application Passwords are a useful feature, but only when you know exactly who created them and why.

The bigger picture

This incident is a warning shot. AI agents that interact directly with WordPress sites are coming from every direction — hosting companies, plugin developers, SaaS platforms. The promise is real: an AI that can diagnose your site, suggest fixes, and handle support questions with full context. But the execution has to respect the same consent boundaries that every other external integration respects.

WordPress's plugin guidelines are clear on this. Section 7 says plugins may not contact external servers without explicit and authorized consent, commonly done via an opt-in method. Automated collection of user data requires explicit confirmation. Rank Math's implementation violated the spirit of those guidelines even if the Application Password mechanism itself is a legitimate WordPress feature.

The lesson for site owners is simple: trust is not a one-time decision. A plugin that was safe yesterday can ship an update tomorrow that changes the deal. Automatic updates are convenient, but they mean you are trusting every plugin author to respect your site's boundaries on every release. For critical sites, consider reviewing changelogs before updating, or at minimum checking your Application Passwords and user capabilities after major plugin updates.

Rank Math says the Support Agent is coming back with proper consent. We will see. For now, revoke those credentials and keep an eye on your profiles.