Wp MapsWordPress extension · Weplugins
CVE-2016-10878
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-google-map-plugin plugin before 3.1.2 for WordPress has XSS.
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-google-map-plugin for WordPress before version 3.1.2 contains a Cross-Site Scripting (XSS) vulnerability. Attackers can inject malicious JavaScript code through unsanitized input fields in the plugin, which then executes in the browsers of users viewing affected pages. This is a stored XSS vulnerability that can lead to session hijacking, credential theft, or malware distribution.
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
< 3.1.2CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm the plugin is installedLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for an entry named 'Wp Google Map Plugin', 'Wp Maps', 'Google Map', or similar mapping plugin from Weplugins.Affected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn the WordPress admin under Plugins > Installed Plugins, find the mapping plugin and click on the plugin name or view details to display the installed version number. Alternatively, check the plugin main file header in wp-content/plugins/ for the 'Version' comment.Affected if The version displayed is below 3.1.2
-
Verify the plugin is activeIn Plugins > Instored Plugins, confirm whether the mapping plugin is currently activated. An inactive plugin may reduce but not eliminate risk if the files remain on the server.Affected if The plugin is activated and accessible to site visitors
-
Inspect plugin-stored data for suspicious contentAccess the WordPress database (via phpMyAdmin or command line) and examine tables that store map plugin data, typically named wp_gm_* or wp_google_maps*. Look for entries containing script tags, javascript:, or other HTML/script injections in fields that accept map labels, descriptions, or coordinates.Affected if Database contains unsanitized script tags or javascript: URIs in plugin-specific tables
The environment is affected if the Weplugins Wp Maps plugin is installed with a version lower than 3.1.2 and contains unsanitized user input in its database tables.
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 data3.1.2
Upgrade the wp-google-map-plugin to version 3.1.2 or later to obtain the patched version. If upgrading is not possible, consider removing the plugin until a fix can be applied.
Fix this in Wp Maps
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10878 — 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-2016-10878 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