WordPress security changelog
HIGH CVE-2026-85200 Received

GEO my WP exposes unauthenticated local file inclusion

GEO my WP through 4.5.5.3 lets an unauthenticated caller select a PHP file for inclusion through gmw_posts_locator_ajax_info_window_loader. The included file executes, enabling access-control bypass, data disclosure, or code execution when an attacker can place PHP on the server. With PEAR and register_argc_argv enabled, the inclusion can itself be chained to write and execute PHP. The authoritative export does not name the file parameter.

CVE / CNA score 7.5 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
GEO my WP
Plugin slug
geo-my-wp
Affected
<= 4.5.5.3
Safe version
See mitigation notes
Published
Sep 12, 2026
Weakness
CWE-98 — Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

This CVE was published Sep 12, 2026 and is one of 10 known issues for this plugin.

What to do

Update, patch or deactivate.

No fixed release is confirmed in the authoritative export. Deactivate the plugin pending a vendor-confirmed fix. The application-level fix must map a strict allowlist of template identifiers to trusted files, reject caller-controlled paths and stream wrappers, and never include files from writable locations.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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.

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

References

Primary and upstream sources