Radar sectionsDatabase
Check my site
WordPress plugin

GEO my WP <= 4.5.5.3 — Unauthenticated Local File Inclusion

CVE-2026-85200Published · Updated

Action summary

Affected: ≤4.5.5.3Update to 4.5.5.4 or newer

All remediation steps
Severity
High7.5
CVSS
7.5
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:H Confidentiality
High
I:N Integrity
None
A:N Availability
None
Weakness
CWE-98 Local File Inclusion
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

GEO my WP geo-my-wp

  1. Affected≤ 4.5.5.3
  2. Patched in4.5.5.4

Update to 4.5.5.4 or newer.

You are affected if you run ≤ 4.5.5.3. Version 4.5.5.4 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under GEO my WP.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 4.5.5.4, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch GEO my WP to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to yck.

The GEO my WP plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.5.5.3 via the gmw_posts_locator_ajax_info_window_loader function. This makes it possible for unauthenticated attackers to include and execute arbitrary .php 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 .php file types can be uploaded and included. In environments where PEAR is installed with register_argc_argv enabled, this file inclusion can be leveraged to write and execute arbitrary PHP code, achieving full remote code execution.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in GEO my WP

All 15
More vulnerabilities in GEO my WP
SeverityVulnerabilityCVEPublished
Medium5.3Missing Authorization
≤4.5.5.5Update to 4.5.5.7
CVE-2026-114193
High8.1Unauthenticated PHP Object Injection
≤4.5.5.3Update to 4.5.5.4
CVE-2026-61992
Medium4.3Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary Geolocation Record Modification and Deletion
≤4.5.5.2Update to 4.5.5.3
CVE-2026-15260
High7.5Unauthenticated SQL Injection
≤4.5.5Update to 4.5.5.1
CVE-2026-52715
High7.5Unauthenticated SQL Injection via 'swlatlng' / 'nelatlng' Parameters
≤4.5.5Update to 4.5.5.1
CVE-2026-9757

Same weakness (Local File Inclusion)

All Local File Inclusion
Other Local File Inclusion vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity high, CVSS 7.5

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?