CVE-2024-3591

Geo Controller <= 8.6.4 - Unauthenticated PHP Object Injection via shortcode REST API Route

2024-02-10 00:00
fuyoumingyan

Strategic Overview

Status
Patched in 8.6.5
Affected Plugin
Geo Controller
Affected Version
<= 8.6.4
CVSS
8.8High
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2024-3591
View all Geo Controller vulnerabilities

At a glance

CVE-2024-3591 is a high-severity Deserialization of Untrusted Data vulnerability in the Geo Controller WordPress plugin, affecting versions <= 8.6.4. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 8.6.5; sites on affected versions should update now. Disclosed February 2024, reported by fuyoumingyan.

Vulnerability Overview

The Geo Controller plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 8.6.4 via deserialization of untrusted input supplied via the '/cache/shortcode' REST API route. This makes it possible for unauthenticated attackers to inject a PHP Object. 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. CVE-2024-30227 is likely a duplicate of this issue.

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. 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 Controller <= 8.6.4 takes no account at all. 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 Controller the fix is 8.6.5: builds <= 8.6.4 are affected, anything from 8.6.5 onward is not.

Remediation

Update to version 8.6.5, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: 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 Controller 8.6.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2024-3591https://www.wordfence.com/threat-intel/vulnerabilities/id/6f00bbab-ef84-42cf-baa7-23c434416981https://nvd.nist.gov/vuln/detail/CVE-2024-3591

Related records

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