Wp Go MapsWordPress extension · Codecabin
CVE-2021-36871
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 · uneditedMultiple Authenticated Persistent Cross-Site Scripting (XSS) vulnerabilities in WordPress WP Google Maps Pro premium plugin (versions <= 8.1.11). Vulnerable parameters: &wpgmaps_marker_category_name, Value > &attributes[], Name > &attributes[], &icons[], &names[], &description, &link, &title.
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 confidenceMultiple authenticated persistent XSS vulnerabilities exist in WP Google Maps Pro premium plugin versions <= 8.1.11. The vulnerable parameters include &wpgmaps_marker_category_name, &attributes[], &icons[], &names[], &description, &link, and &title. An authenticated attacker can inject malicious JavaScript code through these input fields, which is then stored and executed when other users view the affected content.
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
<= 8.1.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Google Maps Pro is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Google Maps Pro' or 'Wp Go Maps' (also check under Plugins > Add New > Upload if recently installed). Alternatively, check the /wp-content/plugins/ directory for a folder named 'wp-google-maps-pro' or similar.Affected if The plugin is present on the WordPress installation
-
Determine the installed version numberIn WordPress admin > Plugins, find the WP Google Maps Pro entry and look for the version number displayed below the plugin name. If not visible there, check the plugin's main PHP file header or readme.txt file in the plugin directory.Affected if Version is displayed as 8.1.11 or lower (any version <= 8.1.11)
-
Confirm the vulnerability is exploitableSince this requires an authenticated attacker, check if any user role other than Administrator has access to the map editing features. Go to WP Google Maps > Edit a Map and examine if Contributor, Author, or Editor roles can access the fields: category name, attributes, icons, names, description, link, or title.Affected if Non-admin users (Authors, Editors, Contributors) have access to map editing functionality and can save map data
You are affected if WP Google Maps Pro version 8.1.11 or lower is installed AND non-admin users have access to map editing features where the vulnerable parameters accept user input.
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.
From vendor dataUpgrade to WP Google Maps Pro version 8.1.12 or later. As a temporary measure, restrict administrative access and implement input sanitization/output encoding on affected endpoints.
Fix this in Wp Go Maps
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36871 — 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-2021-36871 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