CVE-2026-85200
GEO my WP <= 4.5.5.3 - Unauthenticated Local File Inclusion
A public proof of concept exists; no exploitation attested.
- Published2026-09-12
- WeaknessCWE-98
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2026-09-1208:16CVE publishedNVD
Versions per branch
Products declared by the CNA
As Wordfence, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.
- ninjew GEO my WPother versions: not affectedAffected
- ≤ 4.5.5.3no fix statedsemver
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-09-12
Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-85200 yet.
Fix
No fix published by the sources we read yet. NVD record
Detection
read 2026-11-09 09:28 UTC- Nuclei template
- available ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-08
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionnone2026-09-14
- CNACVSS 3.17.5known since 2026-10-23
- CNAweakness (CWE)CWE-98known since 2026-10-23
- FIRST EPSSEPSS score3.2 %2026-11-08
- ProjectDiscoverydetectionread 2026-11-09
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2026-76829same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-6hw9-7gx5-mw88same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Published
- 2026-09-12
- Last Modified
- 2026-09-14
- NVD status
- Deferred
- GitHub Advisory
- GHSA-6hw9-7gx5-mw88
Frequently asked questions
What is CVE-2026-85200?
Is CVE-2026-85200 actively exploited?
What is the CVSS score for CVE-2026-85200?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-6hw9-7gx5-mw88
- Nuclei templates · MIT
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OpenCVE · OpenCVE terms of service · terms restrict redistribution
- CISA Vulnrichment · CC0-1.0