# WP Map Block <= 3.2.0 - Authenticated (Contributor+) Missing Authorization to Sensitive Information Exposure via Maps List REST Endpoint

- **ID:** WPSEC-2026-2410
- **Plugin:** WP Map Block – Google Maps, OpenStreetMap, Mapbox, Store & Shop Locator, Directory, Listings & Filters (`wp-map-block`), https://wordpress.org/plugins/wp-map-block/
- **Affected versions:** from 3.0.0 before 3.2.1
- **Fixed in:** 3.2.1 (Update to 3.2.1 or later.)
- **Severity:** Medium 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N)
- **Weakness:** CWE-862
- **Usage among sites WPSec scans:** plugin Low, affected versions Low (as of 2026-11-03)
- **Attack surface analysis:** https://attacksurface.wpsec.com/plugin/wp-map-block
- **Fix released:** 2026-11-02
- **Published:** 2026-11-03
- **URL:** https://wpsec.com/vuln/WPSEC-2026-2410/

## Description

The WP Map Block plugin for WordPress is vulnerable to unauthorized access of data via the maps list REST endpoint (GET /wpmb/v1/maps) in all versions up to, and including, 3.2.0, due to a missing per-object capability check in the Maps_Controller::index() function. The route only checks the edit_posts capability and then returns a summary of every published and draft map. This makes it possible for authenticated attackers, with Contributor-level access and above, to see the ID, title, map provider, marker count, status and last-modified time of draft maps belonging to other users that they are not permitted to edit.

## References

- https://wpsec.com/vuln/WPSEC-2026-2410/
- https://plugins.svn.wordpress.org/wp-map-block/tags/3.2.1/
- https://wordpress.org/plugins/wp-map-block/

Source: WPSec, https://wpsec.com/vuln/WPSEC-2026-2410/

License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Free to use, share and adapt, also commercially, if you credit WPSec and link to this advisory.