CVE-2024-6330

GEO my WordPress <= 4.5.0.1 - Unauthenticated Local File Inclusion

2024-07-29 00:00
Michael Dyrna

Strategic Overview

Status
Patched in 4.5.0.2
Affected Plugin
GEO my WP
Affected Version
<= 4.5.0.1
CVSS
9.8Critical
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2024-6330
View all GEO my WP vulnerabilities

At a glance

CVE-2024-6330 is a critical-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the GEO my WP WordPress plugin, affecting versions <= 4.5.0.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.5.0.2; sites on affected versions should update now. Disclosed July 2024, reported by Michael Dyrna.

Vulnerability Overview

The GEO my WP plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.5.0.1 via the 'form[info_window_template][content_path]' parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-94: Improper Control of Generation of Code ('Code Injection')

GEO my WP <= 4.5.0.1 carries this weakness at form[info_window_template][content_path], and reaching it takes no account at all. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For GEO my WP the fix is 4.5.0.2: builds <= 4.5.0.1 are affected, anything from 4.5.0.2 onward is not.

Remediation

Update to version 4.5.0.2, 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 my WP 4.5.0.2 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-6330https://www.wordfence.com/threat-intel/vulnerabilities/id/1e65922a-3498-4946-8415-3d922e85e46ahttps://nvd.nist.gov/vuln/detail/CVE-2024-6330

Related records

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