# CVE-2026-8935: Advanced Google Maps < 6.1.1 - Unauthenticated Administrator Account Creation

> Unauthenticated attackers can create administrator accounts and gain full site control via a publicly exposed nonce in the WP MAPS PRO plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-j5mr-6rv3-xgwh

## What is CVE-2026-8935?

CVE-2026-8935 is a critical authentication bypass vulnerability in Unknown WP MAPS PRO, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-8935?


## How do I fix CVE-2026-8935?

No fix has been published for CVE-2026-8935 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8935 being exploited?

There is no known exploitation of CVE-2026-8935 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8935 and fix it if it is affected.

What it is: CVE-2026-8935 is a critical authentication bypass vulnerability in Unknown WP MAPS PRO, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8935 in the wild and no public exploit code.

Affected product: Unknown WP MAPS PRO. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8935/ (Markdown: https://insights.sbomify.com/CVE-2026-8935/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8935
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8935
- OSV: https://osv.dev/vulnerability/CVE-2026-8935

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8935/
Summaries are generated and may contain mistakes; the official description above is the record.