CVE-2026-8385: WP Go Maps · Information Exposure
Affects WP Go MapsSource CVE Database V5
Not known to be exploited · public detection template (Nuclei) · CVSS 5.3 Medium : upgrade to 10.0.10 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.0.10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Jun 2026
Detectable: evidence found.
nuclei template: WordPress WP Go Maps < 10.0.10 - Unauthenticated Marker Data Disclosure
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade WP Go Maps to 10.0.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WP Go Maps | Affected
| Fixed in
|
AI-suggested
Since the vulnerability affects versions before 10.0.10, upgrading to version 10.0.10 or later is likely recommended once confirmed by the vendor. Until then, restrict access to the admin-ajax endpoint or disable the affected datatables functionality if possible.
Description
The WP Go Maps WordPress plugin before 10.0.10 does not properly enforce the marker approval filter on the admin-ajax fallback for its datatables route, allowing unauthenticated visitors to retrieve marker records that the site owner has not approved for public display, including their title, category, address and description fields.