dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-8385

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP Go Maps plugin before version 10.0.10 fails to enforce its marker approval filter on the admin-ajax.php fallback endpoint used by its datatables route. This allows any unauthenticated visitor to query this endpoint and retrieve marker records that have not been approved for public display, exposing sensitive fields including title, category, address, and description.

MitigationUpdate WP Go Maps to version 10.0.10 or later, which implements proper authorization checks on the admin-ajax datatables route to ensure only approved markers are returned to unauthenticated users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP Go Maps plugin is installed
    Access your WordPress admin panel, navigate to Plugins > Installed Plugins, and locate WP Go Maps (also known as Agm Maps or Go Maps) in the list.
    Affected if The plugin is installed and active in WordPress.
  2. Check installed WP Go Maps version
    In the WordPress admin under Plugins > Installed Plugins, find the WP Go Maps plugin and note the version number displayed below the plugin name. Alternatively, check the version in the plugin's main PHP file header.
    Affected if The installed version is lower than 10.0.10.
  3. Test admin-ajax endpoint accessibility
    Using a web browser or curl tool, send a GET request to your site's /wp-admin/admin-ajax.php?action=agm_map_builder_marker&columns=title,category,address,description (or similar datatables request pattern for markers) without logging in.
    Affected if The endpoint responds with marker data without requiring authentication.
  4. Identify unapproved marker records
    Log into WordPress admin and navigate to the WP Go Maps marker management area. Check if there are markers with status 'pending', 'draft', or 'awaiting approval'.
    Affected if There are markers in a non-public approval state in the database.

Your environment is affected if WP Go Maps plugin version is below 10.0.10 AND the admin-ajax endpoint is accessible without authentication AND unapproved markers exist in the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP Go Maps to version 10.0.10 or later, which implements proper authorization checks on the admin-ajax datatables route to ensure only approved markers are returned to unauthenticated users.

Recommended fix Moderate confidence

WP Go Maps version 10.0.10 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WP Go Maps (also known as Go Maps) plugin
  4. Check the current version installed
  5. If the installed version is before 10.0.10, click Update Now to upgrade to the latest version
  6. Alternatively, download version 10.0.10 or later from the WordPress plugin repository and upload manually

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8385 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8385 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data