CVE-2026-85200 json
GEO my WP <= 4.5.5.3 - Unauthenticated Local File Inclusion
published 2026-09-12 57 d ago modified 2026-09-14 55 d ago also EUVD-2026-76829
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.2%
- EPSS 3.2% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
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.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 55 d ago
Exploit prediction
3.23% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template GEO my WP <=4.5.5.3 - Unauthenticated Local File Inclusion nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- ninjew GEO my WP
Classification
- Weakness
-
- CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program
References
- github.com /Fitoussi/geo-my-wp/commit/5a768bf1c6e44ded83a65be8789f3587515665ac
- wordfence.com /threat-intel/vulnerabilities/id/562712a8-a42e-4b36-9985-3c71698efdda?source=cve
- plugins.trac.wordpress.org /browser/geo-my-wp/tags/4.5.5.3/plugins/posts-locator/includes/gmw-posts-locator-functions.php#L975
- plugins.trac.wordpress.org /browser/geo-my-wp/tags/4.5.5.3/plugins/posts-locator/includes/gmw-posts-locator-functions.php#L964
- plugins.trac.wordpress.org /browser/geo-my-wp/tags/4.5.5.3/includes/gmw-functions.php#L1945
- plugins.trac.wordpress.org /browser/geo-my-wp/tags/4.5.5.3/includes/gmw-functions.php#L1987
- plugins.trac.wordpress.org /browser/geo-my-wp/tags/4.5.5.1/plugins/posts-locator/includes/gmw-posts-locator-functions.php#L975
- plugins.trac.wordpress.org /browser/geo-my-wp/tags/4.5.5.1/plugins/posts-locator/includes/gmw-posts-locator-functions.php#L964
- plugins.trac.wordpress.org /browser/geo-my-wp/tags/4.5.5.1/includes/gmw-functions.php#L1945
- plugins.trac.wordpress.org /browser/geo-my-wp/tags/4.5.5.1/includes/gmw-functions.php#L1987
Sources
- CVE List CVE-2026-85200
- NVD CVE-2026-85200
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.