Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach public MapPress embed endpoint
-
DeliveryEnumerate sequential user IDs
-
ExploitTrigger map handler per ID
-
ExecutionHarvest email and display name
-
ImpactAggregate site user PII
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the site run MapPress (versions before 2.97.15) with its front-end map embed feature exposed, which is its normal purpose, so the primary prerequisite is simply that a vulnerable version is installed and serving map embeds publicly. No authentication, user interaction, or special configuration is needed (AV:N/AC:L/PR:N/UI:N), making default deployments exploitable by any remote visitor. The practical limiting factors are: impact is confined to disclosure of user email addresses and display names (no passwords, no code execution, no data modification per C:L/I:N/A:N), and value scales with the number of registered users on the site - a site with few or only administrative accounts yields little, while a membership/community site exposes a large PII set. |
| Impact | This is a genuine but modest-priority issue, not a high-severity emergency. The CVSS 3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N) correctly reflects an unauthenticated, network-reachable information disclosure with only low confidentiality impact and no integrity or availability impact (C:L/I:N/A:N), matching the CWE-200 classification. The signals are internally consistent and point to low-to-moderate real-world risk: EPSS is very low at 0.14% (3rd percentile), SSVC records Exploitation as 'none' (no observed exploitation) with Technical Impact 'partial', and the vulnerability is NOT on CISA KEV. The one aggravating signal is SSVC Automatable:yes - consistent with the description's user-ID enumeration, which can be scripted to harvest all user emails and display names at scale. A public PoC reference exists (WPScan) but it is not verified as working exploit code. The vendor-assigned priority label is 'this_month', aligning with a patch-at-normal-cadence posture rather than immediate action. Net: a real, easily automatable privacy/data-exposure flaw that leaks PII (emails, display names) but grants no code execution or write access - remediate on a normal patch cycle, with some urgency where harvested emails feed phishing or credential-stuffing. |
| Exploit ScenarioDerived | An unauthenticated attacker scripts requests to the MapPress front-end map embed handler, iterating over sequential user IDs, and collects the email address and display name returned for each valid user. Given CVSS AV:N/AC:L/PR:N/UI:N the request requires no authentication, no user interaction, and low complexity, and SSVC marks it Automatable, so the whole site's user roster can be scraped in bulk. A public PoC reference exists (WPScan); it is not verified as working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 01, 2026
Unauthenticated information disclosure in the MapPress WordPress plugin before 2.97.15 allows any remote visitor to enumerate user IDs through the front-end map embed handler and retrieve each matching user's email address and display name. Because the handler does not restrict whose data it renders, exploitation needs no authentication, interaction, or unusual configuration - only a vulnerable version serving map embeds publicly, which is the plugin's normal function. Impact is limited to PII exposure (C:L/I:N/A:N, CVSS 5.3); no public working exploit code has been confirmed (a WPScan reference is available, not verified as working exploit code), EPSS is low at 0.14% (3rd percentile), CISA SSVC records no exploitation, and a vendor patch is available.
RemediationAI
Vendor-released patch: update MapPress to version 2.97.15 or later, which is the first release that restricts the front-end map embed handler to the correct user's data; no separate workaround is documented in the available sources besides running a fixed version. Because the issue is unauthenticated and requires no user interaction, staging the upgrade promptly on community or membership sites - where a large registered-user base maximizes the PII exposure - is the practical priority. After upgrading, review whether user email addresses and display names were harvested by enumerating sequential user IDs. Tracking references are the WPScan entry at https://wpscan.com/vulnerability/ce9f0060-1054-41ca-9543-1508547aab27/ and the NVD detail page at https://nvd.nist.gov/vuln/detail/CVE-2026-118168.
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
The flaw is a CWE-200 information exposure in the front-end map embed handler of the MapPress plugin for WordPress. The handler renders map embeds and resolves user-associated data, but fails to enforce a check on which user's record is being requested, so user IDs supplied to the embed path are resolved and reflected back. Since the affected route is the plugin's public-facing embed functionality, it is reachable without authentication, and WordPress user IDs are sequential and trivially enumerable. The disclosed fields are limited to email address and display name - no passwords, session data, or write access - so the exposure is confidentiality-only. Sites with large registered membership bases have the largest PII footprint, while sites with few or only administrative accounts yield correspondingly little. CPE metadata lists the plugin under an unknown vendor namespace, consistent with a WordPress.org-hosted plugin; EUVD records affected versions as MapPress 0 through <2.97.15.
Know when Mappress 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 remote request to a public embed handler (AV:N/AC:L/PR:N/UI:N) leaking only emails and display names gives C:L with no integrity or availability impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The MapPress WordPress plugin before 2.97.15 does not restrict which user's data its front-end map embed handler renders, allowing unauthenticated visitors to retrieve the email address and display name of any user on the site by enumerating user IDs.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
The mappress-google-maps-for-wordpress plugin before 2.53.9 for WordPress does not correctly implement AJAX functions wi
The MapPress Maps for WordPress plugin before 2.73.13 allows a high privileged user to bypass the DISALLOW_FILE_EDIT and
The MapPress Maps for WordPress plugin before 2.94.9 does not sanitise and escape some parameters when outputing them in
The MapPress Maps for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the width and heig
The MapPress Maps for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the map title para
The MapPress Maps for WordPress plugin before 2.94.10 does not sanitise and escape some of its settings, which could all
The mappress-google-maps-for-wordpress plugin before 2.54.6 for WordPress does not correctly implement capability checks
A vulnerability in chrisvrichardson MapPress Maps for WordPress mappress-google-maps-for-wordpress.85.4. Rated high seve
The MapPress Maps for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'mappress' shortco
The MapPress Maps for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Map b
The MapPress Maps for WordPress plugin before 2.93 does not sanitise and escape some of its settings, which could allow
EUVD-2026-114779
GHSA-wfgm-582m-23r9
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB