Wp MapsWordPress extension · Weplugins
CVE-2015-9305
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.7 for WordPress has XSS related to the add_query_arg() and remove_query_arg() functions.
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 · moderate confidenceThe wp-google-map-plugin for WordPress versions before 2.3.7 contains a cross-site scripting (XSS) vulnerability due to improper usage of WordPress functions add_query_arg() and remove_query_arg(). These functions do not escape output by design, and when developers fail to apply proper output encoding before rendering URLs in HTML contexts, attackers can inject malicious script execution.
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.7CVSS 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.0/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.
-
Locate the wp-google-map-plugin installation directoryNavigate to your WordPress wp-content/plugins/ directory and look for folders named 'wp-google-map-plugin', 'wp-maps', 'wp-google-maps', or 'wp-google-map' - the plugin may also be listed under 'weplugins-wp-maps' or similar naming conventions.Affected if The plugin folder exists in the plugins directory.
-
Determine the installed plugin versionOpen the main plugin PHP file (usually named similarly to the folder, e.g., wp-google-map.php) and locate the version header comment at the top of the file, or check the 'Version' field in the plugin's main PHP file header.Affected if The version listed is less than 2.3.7, or no version header is found (indicating an older unmaintained installation).
-
Verify the vulnerable code pattern existsSearch the plugin source code for occurrences of 'add_query_arg' or 'remove_query_arg' followed by direct output in HTML contexts (e.g., echoed without esc_url(), esc_attr(), or similar WordPress escaping functions). Examine files that handle URL generation, particularly those related to map display or plugin settings pages.Affected if The plugin code uses add_query_arg() or remove_query_arg() without applying proper output encoding (esc_url, esc_attr, esc_html) before rendering in HTML.
You are affected if the Weplugins Wp Maps plugin is installed with a version lower than 2.3.7 and the plugin code contains unescaped add_query_arg/remove_query_arg output in HTML contexts.
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.7
Update the wp-google-map-plugin to version 2.3.7 or later to patch the XSS vulnerability. If an update is unavailable, remove the plugin or implement output encoding on all query argument output.
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-9305 — 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-9305 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