Quick answers
- Is CVE-2026-8386 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-8386 being exploited in the wild.
- How severe is CVE-2026-8386?
- Informational severity, with a CVSS score of 5.3, published 15 June 2026.
- Which products and versions are affected?
- WP Go Maps < 10.0.10.
- Is there a fix for CVE-2026-8386?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-8386 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-8386?
- Check whether you run WP Go Maps at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The WP Go Maps plugin before version 10.0.10 contains an information disclosure vulnerability in its public single-marker REST endpoint. The endpoint fails to verify the 'approved' status of a marker record before returning it to the requester. Because marker IDs are sequential integers, an unauthenticated attacker can enumerate the IDs via the REST API or the AJAX fallback mechanism to retrieve records in the moderation queue. This data includes the address, description, and precise GPS coordinates of markers that were intended to remain private until reviewed by an administrator. The issue is resolved in version 10.0.10.
Affected products
- WP Go Maps WP Go Maps < 10.0.10
Timeline
- 2026-05-25: disclosed: Publicly published by WPScan
- 2026-06-15: advisory: NVD publication date