CVE-2026-19798
Received Received - Intake

Unauthorized Post Status Modification in Wp Map Block Plugin

Publication date: 2026-10-16

Last updated on: 2026-10-16

Assigner: Wordfence

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-16
Last Modified
2026-10-16
Generated
2026-10-16
AI Q&A
2026-10-16
EPSS Evaluated
N/A
NVD
CVE-2026-19798
EUVD
EUVD-2026-102795

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
tusharimran WP Map Block – Google Maps, OpenStreetMap, Mapbox, Store & Shop Locator, Directory, Listings & Filters 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The Wp Map Block plugin for WordPress has a vulnerability due to missing capability checks in the set_status() and bulk() functions. These functions allow authenticated users with Contributor-level access or higher to modify the publish status of any map post, including those owned by administrators. This can lead to unauthorized publishing or unpublishing of maps, affecting site visibility.

Detection Guidance

Check WordPress sites using the Wp Map Block plugin versions up to 3.0.0. Review REST API logs for unauthorized POST requests to /wp-json/wpmb/v1/maps/set_status or /wp-json/wpmb/v1/maps/bulk with Contributor-level or higher access.

Impact Analysis

If exploited, this vulnerability allows attackers to hide published maps from public view or force draft maps to become visible. This could disrupt site functionality, mislead users, or expose sensitive information if maps contain restricted content. Attackers need only Contributor-level access to exploit it.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR or HIPAA if unauthorized changes to map visibility expose protected data or violate data integrity. Unauthorized publishing/unpublishing may result in improper data handling or disclosure, triggering regulatory penalties.

Mitigation Strategies

Update the Wp Map Block plugin to the latest version. Remove Contributor-level access for users unless absolutely necessary. Monitor post status changes in wp_posts table for unauthorized modifications.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-19798. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart