CVE-2026-7624

SEO Plugin by Squirrly SEO <= 12.4.16 - Missing Authorization to Authenticated (Contributor+) Privileged Cloud API Operations

2026-06-05 14:31
Abi Wiranata

Strategic Overview

Status
Patched in 12.4.17
Affected Plugin
GEO Plugin by Squirrly SEO
Affected Version
<= 12.4.16
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-7624
View all GEO Plugin by Squirrly SEO vulnerabilities

At a glance

CVE-2026-7624 is a medium-severity Missing Authorization vulnerability in the GEO Plugin by Squirrly SEO WordPress plugin, affecting versions <= 12.4.16. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 12.4.17; sites on affected versions should update now. Disclosed June 2026, reported by Abi Wiranata.

Vulnerability Overview

The SEO Plugin by Squirrly SEO plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 12.4.16. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to invoke privileged state-changing Squirrly cloud API operations, such as revoking the site's Google Search Console and Google Analytics integrations via `api/gsc/revoke` and `api/ga/revoke`, that are otherwise restricted to administrator-level users holding the `sq_manage_settings` capability.

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 interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in GEO Plugin by Squirrly SEO <= 12.4.16 takes an account at Contributor level or above. 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 12.4.17: builds <= 12.4.16 are affected, anything from 12.4.17 onward is not.

Remediation

Update to version 12.4.17, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: GEO Plugin by Squirrly SEO 12.4.17 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-7624https://www.wordfence.com/threat-intel/vulnerabilities/id/32701ae6-004c-41e2-bdf0-d78c6c2b3e97https://nvd.nist.gov/vuln/detail/CVE-2026-7624

Related records

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