CVE-2026-85200 Details.
GEO my WP <=4.5.5.3 - Unauthenticated Local File Inclusion
Atlas does not check this one. Needs requests that change data.
To test for this one, the check would have to send requests that could change data on the site. Atlas only ever reads public pages, so it does not run this check.
About CVE-2026-85200. What It Means.
GEO my WP WordPress plugin <= 4.5.5.3 contains a local file inclusion caused by improper handling in gmw_posts_locator_ajax_info_window_loader function, letting unauthenticated attackers execute arbitrary PHP code remotely.
Affected Product. What Is Hit.
- Vendor
- developer.developer
- Product
- Developer.developer GEO My WP
References. Where To Read More.
FAQ
Common Questions.
GEO my WP <=4.5.5.3 - Unauthenticated Local File Inclusion. GEO my WP WordPress plugin <= 4.5.5.3 contains a local file inclusion caused by improper handling in gmw_posts_locator_ajax_info_window_loader function, letting unauthenticated attackers execute arbitrary PHP code remotely.
No. To test for this one, the check would have to send requests that could change data on the site. Atlas only ever reads public pages, so it does not run this check. The facts about CVE-2026-85200 are on this page, and you can request a demo to see how Brandefense watches your whole external attack surface.
CVE-2026-85200 is not on the CISA Known Exploited Vulnerabilities list at the time of writing, but it is still worth fixing.
Update Developer.developer GEO My WP to the latest version from the vendor, or follow the vendor's advice to switch off the affected feature. Vendor links are listed on this page when they are known.
This page lists the public facts about CVE-2026-85200. Atlas does not run a check for it, so nothing here says whether a particular site is affected.