Two AIOSEO Vulnerabilities, Two Very Different Threat Models
The AIOSEO vulnerability disclosed this week affects something like two million active installs, which is exactly the kind of number that makes people update first and read second. Both issues are rated Medium (6.5 for CVE-2026-100152, 6.1 for CVE-2026-85492), both are patched in the 5.0.2 line, and both come with conditions that decide whether your particular site is exposed or just running old code. Roger Montti covered the advisory in detail over at Search Engine Journal (opens in new tab), and the conditions are the part worth reading slowly.
The first CVE gets the scarier headline because it needs no account. A missing validation check before the plugin calls WordPress’s do_shortcode means an unauthenticated visitor can get arbitrary shortcodes executed, provided AIOSEO breadcrumbs are being rendered on a search results page through the block, the widget, the shortcode, or a template tag. That caveat is doing a lot of work. If your search template does not print breadcrumbs, I do not think this one reaches you today. If it does, you have a public endpoint that executes whatever a stranger sends it, and that is not a small thing.
The second one is a DOM-based XSS in the SEO Preview panel. An attacker has to craft a URL with a payload in the pathname, and the victim has to hold the aioseo_manage_seo capability and open SEO Preview from the admin toolbar while sitting on that page. It reads like a narrow path, and it is narrower than “unauthenticated XSS” implies, but the target is the account whose compromise costs you the most. A malicious link that fires when your SEO manager clicks Preview is still a malicious link.
There is one wrinkle in the version ranges that I have seen confuse people in support threads. CVE-2026-100152 is listed as affecting everything up to and including 5.0.2, while 5.0.2 is also the release that fixes the XSS. The shortcode fix did not ship until 5.0.2.1, whose changelog reads “Improved security protections for shortcodes on search pages.” So if you stopped at 5.0.2 because a dashboard badge turned green, you closed one door and left the other one open. Check your actual version number, not the update banner.
The analogy I keep coming back to is a faulty front door lock. The shortcode bug is a broken lock on a door that anyone walking past can try. The XSS bug is a broken lock that only matters if you leave the spare key under the mat and only on the days your office manager is in. Both are real. Only one of them is likely to be tested against your site by a scanner tonight.
Background: where the AIOSEO vulnerability sits in the plugin
All in One SEO handles a fair amount of unglamorous plumbing on a WordPress site: XML sitemaps, schema markup, redirects, internal link reports, title and meta templates. Two of its features matter for this advisory, and they sit in very different parts of the codebase.
Breadcrumbs are the small Home > Blog > Post trail. AIOSEO gives you four ways to place them: a Gutenberg block, a classic widget, the [aioseo_breadcrumbs] shortcode, and the aioseo_breadcrumbs() template tag theme authors call directly. All four routes end up in the same rendering code, and that is where CVE-2026-100152 lives. The plugin passed a value through WordPress’s do_shortcode function without validating it first. Wordfence’s advisory is specific about the trigger condition: the AIOSEO breadcrumb has to actually render on a search results page, via one of those four methods, for the flaw to be reachable at all.
do_shortcode is the function WordPress uses to turn or [contact-form-7 id="12"] into rendered output. On a normal page it only ever sees text you typed into the editor. When a value that arrives with the request reaches it unchecked, shortcodes registered by any other plugin on your site become a way to execute things you never meant to run on a page you never wrote. You do not need to understand every shortcode on the site to see why that is a bad place for a missing check.
The XSS bug lives somewhere else entirely. CVE-2026-85492 is DOM-based, which means the vulnerable JavaScript executes in the browser rather than on your server. The URL pathname is read and written into the page without adequate escaping, so a crafted link carries its payload in the path itself. Nothing fires until a logged-in user holding the aioseo_manage_seo capability opens the SEO Preview panel from the admin toolbar while sitting on that page. SEO Preview renders a Google-style snippet so you can eyeball how a post will look in results, and it runs in an admin context, which is exactly why the capability requirement is written into the advisory.
My expectation is that admin-side preview and analysis panels will keep turning up in these reports. They tend to be built quickly, they render data from URLs and request parameters, and they run with more privilege than the front end. If you maintain plugins, that is the surface I would audit first.
The version details and what to do about them are covered here in the Search Engine Journal report (opens in new tab).