dbcve.org
VulnerabilityAwaiting classification

CVE-2026-8935

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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 MAPS PRO WordPress plugin before 6.1.1 registers an unauthenticated AJAX action which, given a valid nonce that is publicly emitted on any frontend page enqueuing its map script, unconditionally creates an administrator account and returns a magic-login URL granting interactive admin access.

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 MAPS PRO plugin before version 6.1.1 registers an unauthenticated AJAX action that creates administrator accounts without any authentication. The required nonce is publicly exposed on frontend pages loading the map script, enabling trivial unauthenticated admin account creation with a returned magic-login URL.

MitigationImmediately update WP MAPS PRO to version 6.1.1 or later. Audit existing administrator accounts for unauthorized entries and revoke any suspicious accounts.

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
High
Integrity
High
Availability
High

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

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 MAPS PRO plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP MAPS PRO' or 'Maps PRO' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active on the WordPress site.
  2. Check the installed version against the affected range
    In the Plugins list, find the version number listed for WP MAPS PRO. Compare it to version 6.1.1. The plugin is vulnerable if the version shown is lower than 6.1.1 (for example, 6.1.0, 6.0.9, etc.).
    Affected if The installed version is before 6.1.1.
  3. Inspect frontend pages for exposed nonce
    View the HTML source of any public page where a map is displayed (look for map container elements or script tags containing 'map' or 'maps'). Search the page source for a nonce value that appears in a JavaScript variable or data attribute related to the map plugin.
    Affected if A nonce value is visible in the frontend page source within map-related script tags.
  4. Check for unauthorized administrator accounts
    In WordPress admin, go to Users > All Users. Review the list for any administrator accounts that you did not create, especially accounts with unfamiliar usernames, random-looking names, or accounts created recently without your knowledge.
    Affected if There exists an administrator account that was not created by you or that you cannot account for.
  5. Review user creation AJAX activity
    If access to server logs or WordPress activity logs is available, search for AJAX calls to wp-admin/admin-ajax.php that include actions related to user creation or admin account creation, particularly from IP addresses you do not recognize.
    Affected if There are logged AJAX requests that created admin users from unknown sources.

The site is affected if WP MAPS PRO version is below 6.1.1 and the plugin is active, regardless of whether you have confirmed the exposed nonce or unauthorized admin accounts yet.

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

Immediately update WP MAPS PRO to version 6.1.1 or later. Audit existing administrator accounts for unauthorized entries and revoke any suspicious accounts.

Recommended fix Moderate confidence

WP MAPS PRO version 6.1.1 or later

  1. 1. Identify all WordPress installations using the WP MAPS PRO plugin.
  2. 2. Verify the current installed version of WP MAPS PRO on each affected site.
  3. 3. If the installed version is before 6.1.1, schedule a maintenance window to apply the update.
  4. 4. Before updating, ensure a complete backup of the WordPress database and files is created.
  5. 5. Update WP MAPS PRO to version 6.1.1 or later through the WordPress admin dashboard or via FTP/SFTP if admin access is unavailable.
  6. 6. After updating, verify that the new version is correctly installed.
  7. 7. Review existing administrator accounts for any unauthorized accounts created by attackers.
  8. 8. Consider resetting passwords for all administrative users as a precautionary measure.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8935 — 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-8935 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