Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site running MapSVG ≤8.16.1
-
ExploitSend unauthenticated request to unprotected endpoint
-
ExecutionBypass missing authorization check
-
ImpactRetrieve embedded sensitive data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The target site must be running the MapSVG (mapsvg-lite-interactive-vector-maps) WordPress plugin at version 8.16.1 or earlier, and must have embedded sensitive data stored within MapSVG maps/content for there to be anything meaningful to disclose. Per the CVSS vector (PR:N/UI:N), no authentication or user interaction is required, so exploitation works against default configurations with only network access to the site. The practical limiting factor is not access control but data exposure scope: impact is confined to confidentiality of data the site operator placed in MapSVG (C:L, no integrity/availability impact), so sites storing only public map data face negligible real impact. |
| Impact | This is a moderate-severity information disclosure issue (CVSS 5.3, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) stemming from a missing authorization check (CWE-862) in the MapSVG WordPress plugin. The CVSS vector signals favor exploitability: network attack vector, low complexity, and no privileges or user interaction required, meaning any unauthenticated remote attacker can trigger it against default installations. However, the impact is bounded - only confidentiality is affected, and only at Low (C:L), with no integrity or availability impact, so this leaks embedded sensitive data rather than enabling takeover. No EPSS score was provided in the input, the CVE is NOT on CISA KEV, and no public proof-of-concept is referenced, so there is no public exploit identified at time of analysis. The signals are internally consistent (easy-to-reach but limited-impact disclosure); the main caveat is that the exact nature and sensitivity of the 'embedded sensitive data' is not detailed, so real-world risk depends on what each site has stored in MapSVG. Treat as a patch-when-practical issue rather than an emergency, prioritizing sites that store sensitive content in maps. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a crafted request to a vulnerable MapSVG endpoint on a WordPress site running the plugin at version 8.16.1 or earlier, where a missing authorization check allows retrieval of embedded sensitive data without login. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, this requires only network reachability to the site and no credentials or victim interaction. No public exploit code is identified at time of analysis, but the low complexity makes reliable exploitation straightforward once the endpoint is known. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
Information disclosure in the MapSVG WordPress plugin (mapsvg-lite-interactive-vector-maps) through version 8.16.1 lets unauthenticated remote attackers retrieve sensitive data that a site has embedded in its MapSVG maps and content, because a missing authorization check (CWE-862) fails to properly gate access to that stored data. Per the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (5.3), no credentials or user interaction are needed and only network reachability to the affected site is required, while impact is confined to confidentiality with no integrity or availability effect and no public exploit identified at time of analysis. Practical risk therefore depends on what operators have placed inside MapSVG content: sites storing only public map data face negligible real impact, whereas those that embedded secrets or private records in map fields should treat this as a live exposure.
RemediationAI
No vendor-released patch version is identified in the available data, so the first step is to check the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/mapsvg-lite-interactive-vector-maps/vulnerability/wordpress-mapsvg-plugin-8-16-1-sensitive-data-exposure-vulnerability?_s_id=cve) and the plugin's WordPress.org page for a fixed release and upgrade to the first version newer than 8.16.1 as soon as it is published. If no fixed release is available and MapSVG is not essential, deactivating and removing the plugin eliminates the exposure entirely, at the cost of losing the interactive maps and any store-locator or directory functionality. If the plugin must stay, apply compensating controls: purge non-public data from MapSVG data objects and custom fields so only information intended for public display remains (this removes the impact even if the authorization gap persists), and add reverse-proxy, WAF, or server rules that block or rate-limit unauthenticated requests to the plugin's data-retrieval endpoints while allowing legitimate page rendering, accepting the trade-off that aggressive blocking can break map loading for normal visitors. Where the site has already been publicly reachable, treat any data previously stored in MapSVG as potentially disclosed and rotate or remove those secrets, and review web logs for enumeration-style requests to plugin endpoints.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
MapSVG is a WordPress plugin that renders interactive vector maps and lets site owners attach custom data objects (locations, directories, store-finder records, and arbitrary custom fields) that are stored and served by the plugin. The root cause is CWE-862 (Missing Authorization): a plugin endpoint or data-retrieval path does not verify that the requester is permitted to read the underlying data, so the authorization decision is effectively skipped rather than enforced. The affected CPE, cpe:2.3:a:pt_norther_lights_production:mapsvg:*:*:*:*:*:*:*:*, uses a wildcard version because the vendor advisory covers all releases from n/a up to and including 8.16.1; the wildcard is not evidence of a broader untested scope. Because the CVSS vector carries PR:N and UI:N, the missing check is reachable over the network without an authenticated session, which is why the issue is tagged as both an authentication bypass and an information-disclosure flaw. The confidentiality-only scoring (C:L, I:N, A:N) reflects that the exposed data is whatever the site operator has stored in MapSVG rather than server-side execution or data modification.
Know when Mapsvg gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Unauthenticated network-reachable missing-authorization flaw (AV:N/AC:L/PR:N/UI:N) yielding limited data disclosure only, so C:L with I:N/A:N and unchanged scope.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Missing Authorization vulnerability in PT Norther Lights Production MapSVG mapsvg-lite-interactive-vector-maps allows Retrieve Embedded Sensitive Data.This issue affects MapSVG: from n/a through 8.16.1.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
The MapSVG WordPress plugin before 6.2.20 does not validate and escape a parameter via a REST endpoint before using it i
MapSVG MapSVG Lite version 3.2.3 contains a Cross Site Request Forgery (CSRF) vulnerability in REST endpoint /wp-admin/a
Unauthenticated SQL injection in the MapSVG WordPress plugin up to version 8.14.0 allows remote attackers to extract sen
SQL injection in the MapSVG WordPress plugin (versions 8.14.0 and earlier) lets remote unauthenticated attackers inject
Arbitrary file upload in the MapSVG WordPress plugin (versions 8.14.0 and earlier) allows an authenticated administrator
SQL injection in the MapSVG WordPress plugin (mapsvg-lite-interactive-vector-maps) affects all versions through 8.16.1 a
SQL injection in the MapSVG WordPress plugin (versions <= 8.14.0) allows an authenticated user holding at least Contribu
SQL injection in the MapSVG WordPress plugin (versions 8.14.0 and earlier) allows Contributor-level authenticated users
Stored cross-site scripting in the MapSVG WordPress plugin (mapsvg-lite-interactive-vector-maps) through version 8.16.1
Cross-site scripting in the MapSVG WordPress plugin (versions 8.14.0 and earlier) allows authenticated Contributor-level
Server-Side Request Forgery in the MapSVG WordPress plugin (versions <= 8.15.0) exposes the hosting WordPress server as
EUVD-2026-102858
GHSA-3r87-gjf6-xw3g
NVD
CVE.org
Vulnrichment
Exploit-DB