CVE-2025-11166
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 · uneditedThe 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.
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 confidenceThe WP Go Maps WordPress plugin up to version 9.0.46 has a CSRF vulnerability where state-changing REST actions are exposed through an AJAX bridge without proper CSRF token validation. Additionally, destructive operations (mass deletion of markers) are reachable via unsafe GET requests with no permission_callback, allowing unauthenticated attackers to delete map data and authenticated admins to be tricked into creating/updating/deleting markers via CSRF.
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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify WP Go Maps plugin versionLocate the plugin in wp-content/plugins/ and open the main PHP file (usually named main.php, class-wp-gomaps.php, or similar) to find the 'Version' header in the plugin comment block, or check via WordPress admin under Plugins > Installed PluginsAffected if The installed version is 9.0.46 or lower
-
Verify REST endpoint configurationInspect the plugin source code for REST API route registrations (look for 'register_rest_route' calls) and check if each route includes a 'permission_callback' argumentAffected if Any state-changing REST routes lack a permission_callback or have one that always returns true without verifying user capabilities
-
Check AJAX action handlers for nonce verificationSearch the plugin files for add_action('wp_ajax_') calls and verify that each handler calls wp_verify_nonce() or check_ajax_referer() before processing state-changing requestsAffected if AJAX handlers that modify data (create/update/delete markers) do not validate CSRF tokens
-
Inspect for unsafe GET-based destructive operationsSearch the plugin code for functions handling marker deletion that respond to $_GET requests, looking for any delete or mass-delete logic that processes $_GET['action'] or similar parameters without requiring a POST requestAffected if The plugin allows deletion of map markers or mass deletion via GET requests without proper authorization checks
A user is affected if the installed WP Go Maps version is 9.0.46 or lower and the plugin exposes REST or AJAX endpoints that lack CSRF token validation, permission callbacks, or allow destructive operations via GET requests.
Generated from the published advisory. Verify against your own configuration.
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 · scopedAdd CSRF token validation to all AJAX and REST endpoints, implement permission_callback for all REST routes, and change destructive GET-based actions to POST-only with proper nonce verification.
9.0.47
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find WP Go Maps (formerly WP Google Maps) in the plugin list
- Click 'Update Now' to update the plugin to the latest version
- Alternatively, go to Dashboard > Updates and update the plugin from there
- After updating, verify the version number shows 9.0.47 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation5.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11166 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11166 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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