HomeWordPress vulnerabilitiesWP Map Block
WP Map Block vulnerabilities
WP Map Block has 3 known vulnerabilities in this database. The most recent published record is dated 16 Oct 2026.
- Known vulnerabilities
- 3
- Active installs
- 20,000+
- Latest version
- 3.2.1
- Last updated
- 2 Nov 2026
- Most recent
- 16 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-19798 | Medium 4.3 | Up to 3.0.0 | Fixed in a later version (latest 3.2.1) | 16 Oct 2026 |
| Cross-site scripting (XSS) CVE-2025-5194 | Medium 4.8 | Before 2.0.3 | Fixed in 2.0.3 | 27 Jun 2025 |
| Cross-site scripting (XSS) CVE-2021-24643 | Medium 5.4 | Before 1.2.3 | Fixed in 1.2.3 | 27 Sep 2021 |
Read the published descriptions
- CVE-2026-19798, 16 Oct 2026
- 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. CVE record
- CVE-2025-5194, 27 Jun 2025
- The WP Map Block WordPress plugin before 2.0.3 does not validate and escape some of its block options before outputting them back in a page/post where the block is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks. CVE record
- CVE-2021-24643, 27 Sep 2021
- 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 CVE record
What to do if you run WP Map Block
If you run WP Map Block, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WP Map Block vulnerabilities
Free. We email you when a new vulnerability is published for WP Map Block, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.