Wp MapsWordPress extension · Weplugins
CVE-2015-9308
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 2.3.10 for WordPress has CSRF in the add/edit map feature.
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 before version 2.3.10 for WordPress contains a Cross-Site Request Forgery (CSRF) vulnerability in the add/edit map feature. This allows attackers to craft malicious requests that trick authenticated administrators into performing unintended actions on the map configuration.
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
< 2.3.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the wp-google-map-plugin installation directoryCheck the /wp-content/plugins/ directory for a folder named 'wp-google-map-plugin' or 'wp-maps' or similar naming conventions used by WepluginsAffected if The plugin folder is present in the WordPress plugins directory
-
Identify the installed plugin versionOpen the main plugin file (usually plugin-name.php) and locate the 'Version' header in the plugin comments, or check the WordPress plugin admin page under Plugins > Installed PluginsAffected if The reported version number is less than 2.3.10 (for example, 2.3.9, 2.3.8, etc.)
-
Verify the plugin is activeIn the WordPress admin dashboard, go to Plugins > Installed Plugins and check if the Wp Maps or wp-google-map-plugin is currently activatedAffected if The plugin shows as 'Active' in the WordPress plugin management page
-
Confirm the add/edit map feature existsCheck if the WordPress admin menu includes a Maps or WP Maps section, or attempt to access the map creation/editing interface via the plugin's admin URLAffected if The add/edit map functionality is present and accessible in the WordPress admin dashboard
A user is affected if the wp-google-map-plugin is installed with a version lower than 2.3.10 and the add/edit map feature is active and accessible.
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 data2.3.10
Update the wp-google-map-plugin to version 2.3.10 or later to remediate the CSRF vulnerability. Additionally, implement anti-CSRF tokens (nonce validation) in the affected add/edit map forms.
Fix this in Wp Maps
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9308 — 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-2015-9308 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