The Wp Map Block plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the setstatus() and bulk() functions in the MapsController REST controller in versions up to, and including, 3.0.0. The plugin's permissioncallback (canedit()) only verifies currentusercan('editposts') and performs no object-level ownership check or verification of publish-level capabilities, while the handlers pass the caller-controlled map ID directly to wpupdatepost() (and wpdeletepost() in the bulk delete branch) to change poststatus 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 wpmbmap post, including maps owned by administrators, which hides published maps from all public pages site-wide or forces draft maps to become publicly visible.

The WP Map Block WordPress plugin before 1.2.3 does not escape some attributes of the WP Map Block, which could allow users with a role as low as contributor to perform Stored Cross-Site Scripting attacks