MapPress Maps for WordPress <= 2.88.15 - Insufficient Authorization to Information Disclosure
Strategic Overview
- Status
- Patched in 2.88.16
- Affected Plugin
- MapPress – Google Maps, OpenStreetMap & Leaflet
- Affected Version
<= 2.88.15- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-0421
At a glance
CVE-2024-0421 is a medium-severity Missing Authorization vulnerability in the MapPress WordPress plugin, affecting versions <= 2.88.15. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.88.16; sites on affected versions should update now. Disclosed January 2024, reported by Erwan LR.
Vulnerability Overview
The MapPress Maps for WordPress plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the mapp_get_post AJAX action in all versions up to, and including, 2.88.15. This makes it possible for unauthenticated attackers to read arbitrary private and draft posts.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in MapPress <= 2.88.15 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For MapPress the fix is 2.88.16: builds <= 2.88.15 are affected, anything from 2.88.16 onward is not.
Remediation
Update to version 2.88.16, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: MapPress 2.88.16 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in MapPress – Google Maps, OpenStreetMap & Leaflet
- 8.8CVE-2023-26015: MapPress Maps for WordPress <= 2.85.4 SQL Injection
CVE-2023-26015 - 8.8CVE-2020-12675: MapPress Maps <= 2.54.5 Remote Code Execution
CVE-2020-12675 - 7.2CVE-2026-56011: MapPress Maps for WordPress <= 2.97.3 Stored XSS
CVE-2026-56011 - 6.5CVE-2020-12077: MapPress Maps for WordPress Map Creation/Deletion
CVE-2020-12077 - 6.4CVE-2025-2055: MapPress Maps for WordPress <= 2.94.8 Stored XSS
CVE-2025-2055 - 6.4CVE-2024-10715: MapPress Maps for WordPress <= 2.94.1 Stored XSS
CVE-2024-10715 - 6.4CVE-2023-7225: MapPress <= 2.88.16 Stored Cross-Site Scripting
CVE-2023-7225 - 6.4CVE-2024-0420: MapPress Maps for WordPress <= 2.88.14 Stored XSS
CVE-2024-0420
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C