Skip to main content
VulnerabilityPublished Updated

CVE-2025-11307: WP Go Maps (formerly WP Google Maps) · Cross-Site Scripting (XSS)

Affects WP Go Maps (formerly WP Google Maps)Source CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.9% chance of exploitation in 30 days – higher than 80% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2025

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
WP Go Maps (formerly WP Google Maps)Affected
  • =0
Fixed in–

AI-suggested

  1. Immediately update the WP Go Maps plugin to version 9.0.48 or later, where this vulnerability is fixed.
  2. If an immediate update is not possible, implement Web Application Firewall (WAF) rules to detect and block malicious AJAX requests targeting the vulnerable endpoints.
  3. Review and harden AJAX handlers in custom WordPress plugins or themes to ensure all user inputs are properly sanitized and validated server-side.
  4. Employ Content Security Policy (CSP) headers to restrict execution of unauthorized scripts in browsers.
  5. Conduct regular security audits and penetration testing focusing on AJAX endpoints and input handling.
  6. Educate site administrators and developers on secure coding practices, especially regarding input sanitization and output encoding.
  7. Monitor web server and application logs for unusual AJAX activity that may indicate exploitation attempts.
  8. Consider implementing multi-factor authentication (MFA) for WordPress admin accounts to reduce impact if session hijacking occurs.
  9. Backup website data regularly to enable quick restoration in case of compromise.
  10. Engage with the plugin vendor or community to track updates and security advisories.

Description

The WP Go Maps (formerly WP Google Maps) WordPress plugin before 9.0.48 does not sanitize user input provided via an AJAX action, allowing unauthenticated users to store XSS payloads which are later retrieved from another AJAX call and output unescaped.

References

Community reviews

Loading reviews…