GEO my WP <= 4.5.4 - Unauthenticated SQL Injection

2026-05-28 00:00

Strategic Overview

Status: Patched in 4.5.5
Affected Plugin: GEO my WP
Affected Version: <= 4.5.4
CVSS: 7.5High
Weakness type: CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE: CVE pending

At a glance

This record tracks a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the GEO my WP WordPress plugin, affecting versions <= 4.5.4. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 4.5.5; sites on affected versions should update now. Disclosed May 2026, reported by N/A.

Vulnerability Overview

The GEO my WP plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 4.5.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in GEO my WP <= 4.5.4 takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For GEO my WP the fix is 4.5.5: builds <= 4.5.4 are affected, anything from 4.5.5 onward is not.

Remediation

Update to version 4.5.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. None of that substitutes for the fix: GEO my WP 4.5.5 closes this, and updating the plugin is the step that ends it.

Firewall
Login Security
Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/5f732a77-fa34-402f-8ab4-a4273b7e0b13

Related records

Same weakness class

Other vulnerabilities in GEO my WP

CVSS Vector

7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityNone
AvailabilityNone

This record contains material that is subject to copyright

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/