dbcve.org
Wp Go MapsWordPress extension · Codecabin

CVE-2021-36870

MEDIUM · 5.4 CVSS v3.1 Published 2021-09-09
Fix available
A fix is available. Upgrade to after 8.1.12 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Multiple Authenticated Persistent Cross-Site Scripting (XSS) vulnerabilities in WordPress WP Google Maps plugin (versions <= 8.1.12). Vulnerable parameters: &dataset_name, &wpgmza_gdpr_retention_purpose, &wpgmza_gdpr_company_name, &name #2, &name, &polyname #2, &polyname, &address.

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

Authenticated persistent XSS in WordPress WP Google Maps plugin (versions <= 8.1.12). Attackers with user accounts can inject malicious JavaScript through eight different parameters (dataset_name, wpgmza_gdpr_retention_purpose, wpgmza_gdpr_company_name, name, polyname, address) that gets stored in the database and executed when other users access map data.

MitigationUpdate WP Google Maps plugin to version >8.1.12. If update unavailable, implement proper input sanitization and output encoding on all affected parameters before storage and display.

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 Go MapsWordPress extension
Affected:<= 8.1.12

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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. Check WP Google Maps plugin version
    Navigate to WordPress Admin > Plugins > Installed Plugins > WP Go Maps (or WP Google Maps) and look at the Version number displayed, or query the WordPress options table: SELECT option_value FROM wp_options WHERE option_name = 'wpgmza_plugin_version' OR option_name = 'wp_google_maps_version';
    Affected if Version is 8.1.12 or lower (or version cannot be determined but plugin is installed)
  2. Verify vulnerable parameters exist in database
    Query the WordPress database for the affected stored parameters. Check the wp_wpgmza (or similar) tables for columns: dataset_name, wpgmza_gdpr_retention_purpose, wpgmza_gdpr_company_name, name, polyname, address. Run: SELECT id, dataset_name, wpgmza_gdpr_retention_purpose, wpgmza_gdpr_company_name, name, polyname, address FROM wp_wpgmza; (table prefix may vary)
    Affected if Database tables and columns exist and contain user-supplied data (indicates the feature is in use)
  3. Inspect stored data for XSS payloads
    Examine the values in the vulnerable columns identified above. Look for patterns indicating unsanitized input: <script> tags, event handlers (onclick, onerror, etc.), javascript: URIs, or encoded XSS vectors. Query: SELECT * FROM wp_wpgmza WHERE dataset_name LIKE '%<%' OR name LIKE '%<%' OR address LIKE '%<%' OR polyname LIKE '%<%';
    Affected if Any records contain raw HTML, script tags, or javascript: prefixes in these fields (indicates XSS is stored and may execute)
  4. Check if user accounts with map editing exist
    Review WordPress user roles. Navigate to Users section and identify any users with Editor, Author, Contributor, or custom roles that have access to map creation/editing in the WP Google Maps plugin.
    Affected if Any authenticated user account exists (even low-privilege) who can access map editing functionality

User is affected if WP Go Maps plugin version is 8.1.12 or lower AND the vulnerable parameters (dataset_name, wpgmza_gdpr_retention_purpose, wpgmza_gdpr_company_name, name, polyname, address) are populated in the database with unsanitized content containing HTML or script tags.

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 a release after 8.1.12
Interim mitigation

Update WP Google Maps plugin to version >8.1.12. If update unavailable, implement proper input sanitization and output encoding on all affected parameters before storage and display.

Recommended fix Moderate confidence

Any version higher than 8.1.12 (check WordPress plugin repository for latest stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'WP Google Maps' (also known as 'Wp Go Maps') plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Verify the update completes successfully
  6. 6. Test that map creation and editing functionality works properly after the update

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

Fix this in Wp Go 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-2021-36870 — 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-2021-36870 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