Skip to main content
Menu
CVEs

RomanCode MapSVG unauthorized access via missing authorization checks

CVE-2026-128997Published , updated

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 9.0.6
Who is exposed
Not reported

Summary

The MapSVG plugin for WordPress, from RomanCode, has a missing authorization flaw that lets an attacker reach functions they should not be able to use. It can be reached remotely over the network without logging in.

Written by a model

Original description

Missing Authorization vulnerability in RomanCode MapSVG mapsvg-lite-interactive-vector-maps allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects MapSVG: from n/a through 9.0.5.

What to do

Upgrade to a fixed version: 9.0.6.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-128997 (WordPress MapSVG plugin <= 9.0.5 - Broken Access Control vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-128997 (entry last updated 2026-11-20):
Affected:
- RomanCode MapSVG: fixed in 9.0.6
Fixed versions: 9.0.6.
Conditions (all must be true for the bug to be hit):
- MapSVG plugin version 9.0.5 or earlier (source: https://patchstack.com/database/wordpress/plugin/mapsvg-lite-interactive-vector-maps/vulnerability/wordpress-mapsvg-plugin-9-0-5-broken-access-control-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-128997 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128997 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/mapsvg-lite-interactive-vector-maps/vulnerability/wordpress-mapsvg-plugin-9-0-5-broken-access-control-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-128997
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-128997
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128997"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

Questions about CVE-2026-128997

Is CVE-2026-128997 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The MapSVG WordPress plugin has a broken access control flaw that lets users reach pages or perform actions they should not be allowed to, such as viewing other people's data.

Source: patchstack.com, cve.org

Which versions are affected by CVE-2026-128997?

mapsvg-lite-interactive-vector-maps: through 9.0.5 (fixed in 9.0.6).

Source: cve.now feed data

Am I affected, and how do I check?

MapSVG plugin version 9.0.5 and earlier are affected. To check, look at the plugin version shown on the WordPress Plugins screen or in the plugin's header in the wp-content/plugins/mapsvg folder.

Source: patchstack.com, cve.org

How do I fix CVE-2026-128997?

Update the MapSVG plugin to version 9.0.6 or later, which is the fixed version named in the advisory.

Source: patchstack.com, cve.org

No corrections so far. Something wrong on this page? Report an error.