# CVE-2026-8732: Privilege escalation in WP Maps Pro

> Unauthenticated attackers can create administrator accounts and take over sites via an insecure AJAX action in WP Maps Pro.

- **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:** 29 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-v837-vph9-gcrq

## What is CVE-2026-8732?

CVE-2026-8732 is a critical vulnerability in flippercode WP Maps Pro, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Maps Pro plugin for WordPress is vulnerable to Privilege Escalation via Administrator Account Creation in all versions up to, and including, 6.1.0. This is due to the wpgmp_temp_access_ajax AJAX action being registered with wp_ajax_nopriv_ and protected only by a nonce check using the fc-call-nonce nonce, which is publicly embedded into every frontend page via wp_localize_script as the nonce field of the wpgmp_local JavaScript object, rendering the check ineffective as an access control mechanism. This makes it possible for unauthenticated attackers to invoke the wpgmp_temp_access_support handler with check_temp=false, which unconditionally creates a new WordPress user with the hardcoded role of administrator via wp_insert_user() and returns a magic login URL that, when visited, calls wp_set_auth_cookie() to fully authenticate the attacker as the newly created administrator, resulting in complete site takeover.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-8732 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8732 exists.

Public exploit code:

- https://github.com/p3Nt3st3r-sTAr/CVE-2026-8732-POC (github_poc): https://github.com/p3Nt3st3r-sTAr/CVE-2026-8732-POC
- CVE-2026-8732 | WP Maps Pro <= 6.1.0 | Unauthenticated Privilege Escalation  (github_poc): https://github.com/zycoder0day/CVE-2026-8732
- WP Maps Pro <= 6.1.0 - Unauthenticated Privilege Escalation via Administrator Account Creation to wpgmp_temp_access_ajax AJAX Action (github_poc): https://github.com/Jenderal92/CVE-2026-8732
- CVE-2026-8732 | WP Maps Pro <= 6.1.0 Unauth Admin Creation (github_poc): https://github.com/fientix/CVE-2026-8732-PoC
- WP Maps Pro <= 6.1.0 - Unauthenticated Privilege Escalation via Administrator Account Creation (github_poc): https://github.com/xShadow-Here/CVE-2026-8732
- CVE-2026-8732 - Draft (WordPress) (github_poc): https://github.com/HORKimhab/CVE-2026-8732

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8732 is a critical vulnerability in flippercode WP Maps Pro, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8732 exists.

Affected product: flippercode 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-8732/ (Markdown: https://insights.sbomify.com/CVE-2026-8732/index.md)
```

## Sources

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

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