LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36870: WordPress WP Google Maps plugin <= 8.1.12 - Multiple Authenticated Persistent XSS vulnerabilities

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.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-36870 is a stored cross-site scripting issue in the WP Google Maps WordPress plugin through version 8.1.12. A privileged authenticated user could save malicious content in map-related fields, causing script execution later in the WordPress site context.

Executive priority

Treat this as a moderate-priority hygiene fix, not an emergency, unless untrusted users hold high WordPress privileges or the site is externally critical.

Technical view

The CVE describes multiple authenticated persistent XSS flaws in WP Google Maps parameters including dataset, GDPR, name, polygon, and address fields. CVSS 3.1 is 5.5: network reachable, low complexity, high privileges required, changed scope, low confidentiality and integrity impact, no availability impact.

Likely exposure

Exposure is limited to WordPress sites using Code Cabin WP Google Maps version 8.1.12 or earlier, especially where multiple administrators or trusted high-privilege users can edit map data.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Abuse requires authenticated high privileges, so the most realistic scenario is a malicious or compromised privileged WordPress account planting persistent script content.

Researcher notes

Evidence supports authenticated stored XSS in specific plugin parameters, but the bundle does not provide exploit proof, active exploitation, or precise remediation version. Avoid assuming public weaponization without additional sources.

Mitigation direction

  • Inventory WordPress sites using the WP Google Maps plugin.
  • Upgrade WP Google Maps beyond 8.1.12 after confirming vendor guidance.
  • Restrict plugin and map-editing access to trusted administrators only.
  • Review existing map, polygon, address, dataset, and GDPR fields for unexpected script content.
  • Monitor vendor, WordPress plugin, and Patchstack pages for definitive fixed-version guidance.

Validation and detection

  • Check each WordPress instance for the installed WP Google Maps plugin version.
  • Confirm no production site remains on version 8.1.12 or earlier.
  • Review administrator and high-privilege account activity around map content changes.
  • Inspect affected stored fields for suspicious HTML or script-like values.
  • After updating, verify normal map functionality and stored content rendering.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-36870 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2021-36870Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Code Cabin IncWP Google Maps (WordPress plugin)8.1.12Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.