CVE-2026-8386: 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.7% chance of exploitation in 30 days – higher than 54% 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: WP Go Maps < 10.0.10 - Unauthenticated Marker Information 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
If you cannot patch yet, consider restricting access to the REST endpoint or implementing custom approval-state filtering to prevent exposure of unapproved marker data.
Description
CVE-2026-8386 is an information exposure vulnerability in the WP Go Maps WordPress plugin before version 10.0.10. The plugin's public single-marker REST endpoint does not filter markers by approval state, allowing unauthenticated users to access marker data that administrators have not approved for public display. This data may include personally identifiable information (PII) in address and description fields, as well as geographic coordinates. The vulnerability has a medium severity with a CVSS score of 5.3.