Skip to content
Surfilby Adam Hafez

All in One SEO plugin patched for two vulnerabilities

Two All in One SEO flaws, CVE-2026-100152 (shortcode execution) and CVE-2026-85492 (XSS), are fixed in version 5.0.2.1. What each one needs to work.

Published · 2 min read

Written byAdam Hafez
A brass padlock and a steel chain fastened across weathered grey wooden planks

Key takeaways

  • CVE-2026-100152 lets an unauthenticated visitor run arbitrary shortcodes in versions up to 5.0.2, but only where the plugin's breadcrumb renders on the search results page.
  • CVE-2026-85492 is a DOM-based XSS flaw in versions up to 5.0.1.1, and it needs a user with the aioseo_manage_seo capability to open SEO Preview on a crafted URL.
  • Wordfence scored the shortcode flaw 6.5 and the scripting flaw 6.1, both medium, and the plugin's changelog places the fixes in 5.0.2 and 5.0.2.1.
  • The fix for the shortcode flaw is in 5.0.2.1, so a site on 5.0.2 is still exposed, and version 5.0.3, dated 7 October 2026, was the latest release when we checked.
  • Search Engine Journal reports the plugin has more than 2 million active installations, which is why the update matters even though both flaws need specific conditions.

Search Engine Journal’s Roger Montti reported on 12 October 2026 that two security vulnerabilities were disclosed in the All in One SEO (AIOSEO) WordPress plugin, which he puts at more than 2 million active installations. We fetched the CVE records for both from the CIRCL CVE API. Wordfence is the assigning authority on each, and the figures below come from those records and the plugin’s changelog on WordPress.org. Wordfence’s own advisory pages returned a bot check when we requested them, so we did not read those pages.

What is CVE-2026-100152?

It is an unauthenticated arbitrary shortcode execution flaw. The Wordfence record says all versions up to and including 5.0.2 are affected, and it scores the flaw 6.5, which is medium. The cause, in the record’s words, is that the plugin does not properly validate a value before running do_shortcode.

The record adds a condition: the plugin’s breadcrumb has to be rendered on the search results page, through the block, widget, shortcode or template tag. Montti notes this means the exposure depends on how a site uses breadcrumbs, even though no login is needed. If you use breadcrumb markup from the plugin on a search template, you are the case the record describes.

What is CVE-2026-85492?

It is a DOM-based cross-site scripting flaw reached through a URL pathname. The record lists versions up to and including 5.0.1.1 and scores it 6.1, also medium. It names insufficient input sanitization and output escaping as the cause.

Exploitation is narrower still. The victim must hold the aioseo_manage_seo capability and open the SEO Preview panel in the admin toolbar while visiting a page with a crafted URL, per the record. Montti points out that visiting such a URL is not enough on its own.

Which version fixes them?

The Wordfence records state the affected ranges, not the patched release. The fixed versions come from the plugin’s changelog on WordPress.org, which Montti also quotes:

  • 5.0.2: lists “Improved security and access protections in SEO Revisions, SEO Analysis and the SEO Preview”, which is the release the record’s changeset reference points to for the scripting flaw.
  • 5.0.2.1: lists “Improved security protections for shortcodes on search pages”, the fix for the shortcode flaw.

A site on 5.0.2 therefore has the scripting fix but not the shortcode fix. The plugin directory listed 5.0.3 as the latest release when we checked, dated 7 October 2026, so a current install is past both.

What should site owners do?

Update the plugin to 5.0.2.1 or later, which is also Montti’s recommendation. Open Plugins in the WordPress admin, confirm the AIOSEO version, and update if it shows 5.0.2 or lower.

Neither record describes active attacks, and both flaws need conditions that many sites will not meet: breadcrumbs on a search template for the first, a privileged user opening the preview on a crafted link for the second. That is a reason to update on your normal schedule this week, not a reason to panic. For where this fits in a site’s wider health, see technical SEO.

The evidence

Type
industry
Impact
medium
Affects
All in One SEO plugin, WordPress sites, Breadcrumbs on search results pages, SEO Preview panel

Sources

  1. 1.CVE-2026-100152: All in One SEO <= 5.0.2 - Unauthenticated Arbitrary Shortcode Execution - Wordfence (CVE record, via the CIRCL CVE API), October 3, 2026Primary
  2. 2.CVE-2026-85492: All in One SEO <= 5.0.1.1 - Reflected DOM-Based Cross-Site Scripting via URL Pathname - Wordfence (CVE record, via the CIRCL CVE API), October 2, 2026Primary
  3. 3.All in One SEO plugin changelog - WordPress.org Plugin DirectoryPrimary
  4. 4.All In One SEO WordPress Plugin Vulnerable To Two Exploits - Search Engine Journal, October 12, 2026

Common questions

Which All in One SEO versions are affected?

CVE-2026-100152 affects all versions up to and including 5.0.2 and is fixed in 5.0.2.1. CVE-2026-85492 affects versions up to and including 5.0.1.1 and is fixed in 5.0.2. Version 5.0.2.1 or later covers both.

Can someone exploit the shortcode flaw without an account?

Per the Wordfence record, yes, an unauthenticated visitor can trigger it. It also requires the plugin's breadcrumb to be rendered on the search results page, through the block, widget, shortcode or template tag.

How severe are the two vulnerabilities?

Wordfence's CVE records give the shortcode flaw a CVSS score of 6.5 and the scripting flaw 6.1, both medium. Neither is rated high or critical.

What should I do?

Update All in One SEO to 5.0.2.1 or a newer release from the WordPress plugin screen, or let auto-updates do it. The WordPress.org listing showed 5.0.3, dated 7 October 2026, as the latest version when we checked.

About the author

Adam Hafez
Adam Hafez

Founder, UpgradIQ FZC LLC

Adam Hafez works on technical SEO and search measurement: how pages get crawled, indexed, ranked and now quoted by answer engines. He founded UpgradIQ, which reads Google Search Console and GA4 to tie ranking movement back to the changes that caused it. He publishes what the data supports and states the limits of it.

  • Technical SEO
  • Search Console and GA4
  • Answer engine optimization
  • Structured data

The briefing

Only what actually changed in search, delivered in full by RSS, Atom or JSON feed.

Follow