GEO Plugin by Squirrly SEO <= 14.2.5 - Authenticated (Contributor+) PHP Object Injection
Strategic Overview
- Status
- Patched in 14.2.6
- Affected Plugin
- GEO Plugin by Squirrly SEO
- Affected Version
<= 14.2.5- CVSS
- 7.5High
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2026-94076
At a glance
CVE-2026-94076 is a high-severity Deserialization of Untrusted Data vulnerability in the GEO Plugin by Squirrly SEO WordPress plugin, affecting versions <= 14.2.5. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 14.2.6; sites on affected versions should update now. Disclosed September 2026, reported by Ananda Dhakal.
Vulnerability Overview
The GEO Plugin by Squirrly SEO plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 14.2.5. This is due to deserialization of untrusted input. This makes it possible for authenticated attackers, with contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-502: Deserialization of Untrusted Data
Reaching this weakness in GEO Plugin by Squirrly SEO <= 14.2.5 takes an account at Contributor level or above. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.
A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For GEO Plugin by Squirrly SEO the fix is 14.2.6: builds <= 14.2.5 are affected, anything from 14.2.6 onward is not.
Remediation
Update to version 14.2.6, or a newer patched version
How does WordSec protect against this?
An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: GEO Plugin by Squirrly SEO 14.2.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in GEO Plugin by Squirrly SEO
- 8.8CVE-2024-6497: SEO Plugin by Squirrly SEO <= 12.3.19 SQL Injection
CVE-2024-6497 - 8.8CVE-2022-38140: SEO Plugin by Squirrly SEO Arbitrary File Upload
CVE-2022-38140 - 7.5SEO Plugin by Squirrly SEO < 6.1.5 Directory Traversal
- 7.3SEO Plugin by Squirrly SEO < 6.1.5 Missing Authorization Checks
- 7.2CVE-2026-66614: GEO Plugin by Squirrly SEO <= 14.2.2 Stored XSS
CVE-2026-66614 - 7.2CVE-2026-1667: SEO Plugin… Arbitrary Post Creation and Stored XSS
CVE-2026-1667 - 6.5CVE-2025-22783: SEO Plugin by Squirrly SEO <= 12.4.03 SQL Injection
CVE-2025-22783 - 6.5CVE-2025-1768: SEO Plugin by Squirrly SEO <= 12.4.05 SQL Injection
CVE-2025-1768
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C