dbcve.org
Wp MapsWordPress extension · Weplugins

CVE-2022-25600

HIGH · 8.8 CVSS v3.1 Published 2022-03-11
Fix available
A fix is available. Upgrade to 4.2.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability affecting Delete Marker Category, Delete Map, and Copy Map functions in WP Google Map plugin (versions <= 4.2.3).

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

Cross-Site Request Forgery (CSRF) vulnerability in WP Google Map plugin versions <= 4.2.3 allows attackers to trick authenticated administrators into unknowingly executing Delete Marker Category, Delete Map, and Copy Map functions via malicious links or sites.

MitigationUpdate WP Google Map plugin to a version newer than 4.2.3, or implement anti-CSRF tokens/nonces in the three affected functions as an interim fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp MapsWordPress extension
Affected:< 4.2.4
FedoraOperating system
Affected:= 34= 35= 36

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Google Map plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WP Google Map' or 'WPGMap' plugin in the list
    Affected if The plugin is not installed or has been removed
  2. Check installed plugin version
    In Plugins list, click on the WP Google Map plugin to view version details, or inspect the plugin header in /wp-content/plugins/wp-google-map-plugin/ folder via file manager or FTP
    Affected if Version is 4.2.3 or lower
  3. Confirm admin user accounts exist
    Go to WordPress admin > Users and verify if any users with Administrator role exist
    Affected if No administrator accounts are present (CSRF requires an authenticated admin to be tricked)
  4. Inspect vulnerable function nonces
    Access plugin source code files (typically map-functions.php or admin-menu.php) and search for the functions 'delete_marker_category', 'delete_map', and 'copy_map'. Verify if these actions check for wp_verify_nonce or wp_create_nonce before execution
    Affected if These functions lack nonce/token validation (vulnerable to CSRF)

User is affected if WP Google Map plugin version 4.2.3 or lower is installed AND administrator users exist who could be tricked into clicking malicious links

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
Upgrade available Upgrade to 4.2.4 or later
Fixed in 4.2.4
Interim mitigation

Update WP Google Map plugin to a version newer than 4.2.3, or implement anti-CSRF tokens/nonces in the three affected functions as an interim fix.

Recommended fix High confidence

WP Google Map plugin version 4.2.4 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'WP Google Map' plugin (may also be listed as 'Maps' or 'Wp Maps')
  4. 4. If an update is available, click 'Update Now' to upgrade to version 4.2.4 or later
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin to manually upload the fixed version if automatic update is unavailable
  6. 6. After updating, verify the plugin version shows 4.2.4 or higher under Plugins > Installed Plugins
  7. 7. Test the Delete Marker Category, Delete Map, and Copy Map functions to confirm they work correctly

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

Fix this in Wp Maps Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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