Security readout for executives and security teams
Plain-English summary
This CVE concerns a cross-site scripting issue in a WordPress Google Maps plugin before version 2.3.7. If a site still runs an affected plugin version, an attacker may be able to make the site render attacker-controlled script. The public bundle does not provide severity, CVSS, exploit detail, or confirmed active exploitation.
Executive priority
Handle as an inventory-driven cleanup item unless the plugin is found on important public WordPress sites. The business urgency rises if administrators or customers use affected pages, but current sources do not support a critical rating or active-exploitation claim.
Technical view
CVE-2015-9305 describes XSS in wp-google-map-plugin before 2.3.7 related to WordPress add_query_arg() and remove_query_arg() handling. The sources do not specify whether the flaw is reflected or stored, whether authentication is required, which endpoints are affected, or what user interaction is needed.
Likely exposure
Exposure is likely limited to WordPress sites that installed wp-google-map-plugin and have not upgraded beyond versions before 2.3.7. The provided affected-product metadata is incomplete, so inventory should be based on plugin name and installed version evidence.
Exploitation context
The source bundle does not cite CISA KEV listing or any public active-exploitation evidence. Because this is XSS in a WordPress plugin, realistic impact depends on where the vulnerable output appears and who can trigger or view it.
Researcher notes
Evidence is sparse: no CVSS, CWE, vulnerable endpoint, exploit preconditions, or patch notes are included in the bundle. The key technical clue is unsafe handling around add_query_arg() and remove_query_arg(), a known WordPress XSS pitfall when output is not escaped.
Mitigation direction
- Inventory WordPress sites for wp-google-map-plugin installations and versions.
- Upgrade wp-google-map-plugin to version 2.3.7 or later where available.
- Remove or disable the plugin if it is unused or unsupported.
- Review the WordPress plugin developer page for current vendor guidance.
- Prioritize externally reachable WordPress sites and administrative user exposure.
Validation and detection
- Check each WordPress instance for the plugin slug wp-google-map-plugin.
- Record installed plugin versions and compare against version 2.3.7.
- Confirm public pages using the plugin no longer render unsafe script output.
- Review access logs for unusual requests to pages using the plugin.
- Document whether the plugin remains business-required after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2015-9305 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/wp-google-map-plugin/#developersCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.