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.
Published: 2026-10-16
Score: 4.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized modification of map posts via REST API
Action: Apply patch
AI Analysis

Impact

The plugin lacks a proper capability check on the set_status() and bulk() functions in the Maps_Controller REST controller. The permission callback verifies only that the user can edit posts, without checking ownership or publish rights. As a result, any authenticated user with Contributor level or higher can send REST requests to change the post_status of any wpmb_map post, including those belonging to administrators, or delete them. The flaw is a classic missing authorization weakness, classified as CWE‑862.

Affected Systems

WordPress sites running the WP Map Block plugin version 3.0.0 or earlier, maintained by the vendor tusharimran, are impacted. Users with Contributor or higher roles on those installations can exploit the missing authorization check.

Risk and Exploitability

The CVSS score of 4.3 indicates moderate severity, and the vulnerability is not listed in the CISA KEV catalog. EPSS shows a value of < 1%, indicating a very low but non‑zero likelihood of exploitation. The likely attack vector is an authenticated REST API request from a user with Contributor level or higher; privilege escalation is not required. Because the flaw operates through standard WordPress REST endpoints, an attacker can reach the vulnerable functions readily once authenticated, making the issue a moderate but actionable risk.

Generated by OpenCVE AI on October 16, 2026 at 15:22 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update WP Map Block to the latest version, which includes a fixed authorization check for set_status() and bulk() endpoints.
  • If an immediate upgrade is not possible, restrict the REST routes for map status changes by removing them for non‑administrators or by disabling them through a security plugin or custom code.
  • Reconfigure user roles so that only administrators or users with publish capabilities can manage map posts; downgrade or remove Contributor access on sites that do not need map publishing functionality.

Generated by OpenCVE AI on October 16, 2026 at 15:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 16 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 16 Oct 2026 07:00:00 +0000

Type Values Removed Values Added
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.
Title WP Map Block <= 3.0.0 - Missing Authorization to Authenticated (Contributor+) Arbitrary Map Publish/Unpublish/Delete via set_status() and bulk() REST Endpoints
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-10-16T14:22:54.237Z

Reserved: 2026-08-13T19:47:58.655Z

Link: CVE-2026-19798

cve-icon Vulnrichment

Updated: 2026-10-16T14:22:41.019Z

cve-icon NVD

Status : Deferred

Published: 2026-10-16T07:17:13.217

Modified: 2026-10-16T15:17:15.747

Link: CVE-2026-19798

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-16T15:30:14Z

Weaknesses