# CVE-2025-11166: WP Go Maps (formerly WP Google Maps) <= 9.0.46 - Cross-Site Request Forgery to Plugin Settings Update

> Unauthenticated attackers can force logged-in administrators to modify or delete map markers and geometry features via CSRF attacks.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8j57-89fx-hmh4

## What is CVE-2025-11166?

CVE-2025-11166 is a medium-severity vulnerability in wpgmaps WP Go Maps (formerly WP Google Maps), published on 9 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The WP Go Maps (formerly WP Google Maps) plugin for WordPress is vulnerable to Cross-Site Request Forgery (CSRF) in all versions up to, and including, 9.0.46. This is due to the plugin exposing state-changing REST actions through an AJAX bridge without proper CSRF token validation, and having destructive logic reachable via GET requests with no permission_callback. This makes it possible for unauthenticated attackers to force logged-in administrators to create, update, or delete markers and geometry features via CSRF attacks, and allows anonymous users to trigger mass deletion of markers via unsafe GET requests.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2025-11166?


## How do I fix CVE-2025-11166?

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

## Is CVE-2025-11166 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11166 and fix it if it is affected.

What it is: CVE-2025-11166 is a medium-severity vulnerability in wpgmaps WP Go Maps (formerly WP Google Maps), published on 9 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-11166 in the wild and no public exploit code.

Affected product: wpgmaps WP Go Maps (formerly WP Google Maps). 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-2025-11166/ (Markdown: https://insights.sbomify.com/CVE-2025-11166/index.md)
```

## Sources

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

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