CVE-2026-1667

SEO Plugin by Squirrly SEO <= 14.0.0 - Unauthenticated Arbitrary Post Creation and Stored Cross-Site Scripting via savePost()

2026-07-10 04:12
Osvaldo Noe Gonzalez Del Rio (Os)

Strategic Overview

Status
Patched in 14.0.1
Affected Plugin
GEO Plugin by Squirrly SEO
Affected Version
<= 14.0.0
CVSS
7.2High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-1667
View all GEO Plugin by Squirrly SEO vulnerabilities

At a glance

CVE-2026-1667 is a high-severity Missing Authorization vulnerability in the GEO Plugin by Squirrly SEO WordPress plugin, affecting versions <= 14.0.0. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 14.0.1; sites on affected versions should update now. Disclosed July 2026, reported by Osvaldo Noe Gonzalez Del Rio (Os).

Vulnerability Overview

The SEO Plugin by Squirrly SEO plugin for WordPress is vulnerable to Arbitrary Post Creation and Stored Cross-Site Scripting in all versions up to, and including, 14.0.0 due to a leak of an API token and insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to create arbitrary posts, and, if the Advanced Custom Fields plugin is installed and activated, inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in GEO Plugin by Squirrly SEO <= 14.0.0 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For GEO Plugin by Squirrly SEO the fix is 14.0.1: builds <= 14.0.0 are affected, anything from 14.0.1 onward is not.

Remediation

Update to version 14.0.1, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: GEO Plugin by Squirrly SEO 14.0.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-1667https://www.wordfence.com/threat-intel/vulnerabilities/id/aebdd464-10b9-4d43-bf38-f0e8ae25625fhttps://nvd.nist.gov/vuln/detail/CVE-2026-1667

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C