The Wp Map Block plugin for WordPress is vulnerable to unauthorized modification of data due to a...
🔗 CVE IDs covered (1)
📋 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.
🔗 References (8)
- https://nvd.nist.gov/vuln/detail/CVE-2026-19798
- https://plugins.trac.wordpress.org/browser/wp-map-block/tags/3.0.0/includes/Rest/Maps_Controller.php#L124
- https://plugins.trac.wordpress.org/browser/wp-map-block/tags/3.0.0/includes/Rest/Maps_Controller.php#L237
- https://plugins.trac.wordpress.org/browser/wp-map-block/tags/3.0.0/includes/Rest/Maps_Controller.php#L262
- https://plugins.trac.wordpress.org/browser/wp-map-block/tags/3.0.0/includes/Rest/Maps_Controller.php#L63
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3730836%40wp-map-block&new=3730836%40wp-map-block
- https://www.wordfence.com/threat-intel/vulnerabilities/id/b42f1f71-e272-48d4-9b3f-4360b287e16f?source=cve
- https://github.com/advisories/GHSA-5899-9734-mqjw