Answer in brief
CVE-2026-85200 records a Unknown severity vulnerability in GEO my WP <= 4.5.5.3 - Unauthenticated Local File Inclusion. The current sources do not mark it as known exploited. The current feed maps ninjew/GEO my WP (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps ninjew/GEO my WP (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ninjew/GEO my WPgeneric | 0 | Not reported |
Published upstream
Sep 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 12, 2026
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.
Quoted source text, attributed separately from HOL analysis.