fixnx
mediumCVE-2025-9205

MapSVG Lite <= 8.14.0 - Authenticated (Contributor+) Stored Cross-Site Scripting

The MapSVG plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 8.14.0. This is due to insufficient input sanitization and output escaping on user supplied attributes within the map options. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Browse WordPress security risks
ProductMapSVG – Vector maps, Image maps, Google Maps
CVSS6.4
EPSSNot scored yet
UpdatedJuly 24, 2026

Quick answer

oyatek MapSVG – Vector maps, Image maps, Google Maps should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • <= 8.14.0
  • up to and including 8.14.0

Fixed versions

  • 8.14.1

How to fix it

CVE-2025-9205 affects MapSVG – Vector maps, Image maps, Google Maps and involves cross-site scripting. Successful exploitation may run attacker-controlled script in a trusted user's browser and expose session or application data. Prioritize deployments that process untrusted input, expose the affected feature, or hold sensitive data. Upgrade MapSVG – Vector maps, Image maps, Google Maps to 8.14.1 or a later vendor-supported fixed release.

  1. Inventory every deployment, device, package, plugin, container, build, and environment that uses MapSVG – Vector maps, Image maps, Google Maps.
  2. Compare the installed version with the recorded affected range: <= 8.14.0, *-8.14.0.
  3. Upgrade MapSVG – Vector maps, Image maps, Google Maps to 8.14.1 or a later vendor-supported fixed release.
  4. Until patched, disable the affected MapSVG – Vector maps, Image maps, Google Maps feature or plugin and restrict its public and administrator endpoints.
  5. Review configuration, roles, tokens, network paths, and exposed endpoints connected to MapSVG – Vector maps, Image maps, Google Maps; remove access that is not required.
  6. Review submissions, stored content, administrator activity, CSP reports, and web logs for script payloads or suspicious browser requests.
  7. If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2025-9205 in place.
  • Use a safe regression test to confirm the affected cross-site scripting path no longer produces the vulnerable behavior.
  • Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
  • Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
  • Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.

Related categories

WordPressCross-site Scripting

Related security risks

More published guidance from the same primary category.

medium

CVE-2026-65475 Modula Image Gallery vulnerability

Updated July 24, 2026

high

CVE-2026-65511 Manual - Documentation, Knowledge Base & Education WordPress Theme vulnerability

Updated July 24, 2026

medium

CVE-2026-65522 Manual - Documentation, Knowledge Base & Education WordPress Theme vulnerability

Updated July 24, 2026

Trusted references

Source advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceWordfence advisoryNVD, WordfenceWordfence advisoryNVD, Wordfence

FAQ

What is affected by CVE-2025-9205?

oyatek MapSVG – Vector maps, Image maps, Google Maps versions listed as affected should be reviewed: <= 8.14.0, up to and including 8.14.0.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.