Description
The Wp Map Block plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the set_status() and bulk() functions in the Maps_Controller REST controller in versions up to, and including, 3.0.0. The plugin's permission_callback (can_edit()) only verifies current_user_can('edit_posts') and performs no object-level ownership check or verification of publish-level capabilities, while the handlers pass the caller-controlled map ID directly to wp_update_post() (and wp_delete_post() in the bulk delete branch) to change post_status between publish and draft. This makes it possible for authenticated attackers, with Contributor-level access and above, to publish or unpublish (and bulk-delete) any wpmb_map post, including maps owned by administrators, which hides published maps from all public pages site-wide or forces draft maps to become publicly visible.
References6
- plugins.trac.wordpress.org/browser/wp-map-block/tags/3.0.0/incl…
- plugins.trac.wordpress.org/browser/wp-map-block/tags/3.0.0/incl…
- plugins.trac.wordpress.org/browser/wp-map-block/tags/3.0.0/incl…
- plugins.trac.wordpress.org/browser/wp-map-block/tags/3.0.0/incl…
- plugins.trac.wordpress.org/changeset?reponame=&old=3730836%40wp…
- www.wordfence.com/threat-intel/vulnerabilities/id/b42f1f71-e272…
Metrics
- CVSS 3.1
-
4.3
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N - EPSS — exploit probability
- 0% percentile: 10 · as of 10 November 2026
- CWE
- CWE-862
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.