CVE-2026-7624 json
SEO Plugin by Squirrly SEO <= 12.4.16 - Missing Authorization to Authenticated (Contributor+) Privileged Cloud API Operations
published 2026-06-06 5 mo ago modified 2026-07-23 3 mo ago also EUVD-2026-34956
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected products
- cifi SEO Plugin by Squirrly SEO
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/32701ae6-004c-41e2-bdf0-d78c6c2b3e97?source=cve
- plugins.trac.wordpress.org /browser/squirrly-seo/trunk/controllers/Post.php#L683
- plugins.trac.wordpress.org /browser/squirrly-seo/tags/12.4.16/controllers/Post.php#L683
- plugins.trac.wordpress.org /browser/squirrly-seo/trunk/controllers/Post.php#L680
- plugins.trac.wordpress.org /browser/squirrly-seo/tags/12.4.16/controllers/Post.php#L680
- plugins.trac.wordpress.org /browser/squirrly-seo/trunk/classes/RemoteController.php#L573
- plugins.trac.wordpress.org /browser/squirrly-seo/tags/12.4.16/classes/RemoteController.php#L573
- plugins.trac.wordpress.org /browser/squirrly-seo/trunk/classes/RemoteController.php#L51
- plugins.trac.wordpress.org /browser/squirrly-seo/tags/12.4.16/classes/RemoteController.php#L51
- plugins.trac.wordpress.org /browser/squirrly-seo/tags/12.4.15/controllers/Post.php#L683
- plugins.trac.wordpress.org /browser/squirrly-seo/tags/12.4.15/controllers/Post.php#L680
- plugins.trac.wordpress.org /browser/squirrly-seo/tags/12.4.15/classes/RemoteController.php#L573
- plugins.trac.wordpress.org /browser/squirrly-seo/tags/12.4.15/classes/RemoteController.php#L51
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3558846%40squirrly-seo&new=3558846%40squirrly-seo&sfp_email=&sf
Sources
- CVE List CVE-2026-7624
- NVD CVE-2026-7624
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.