<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 23 Oct 2026 22:23:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-19798 — WP Map Block &lt;= 3.0.0 - Missing Authorization to Authenticated (Contributor+) Arbitrary Map Publish/Unpublish/Delete vi…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-19798</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; tusharimran WP Map Block – Google Maps, OpenStreetMap, Mapbox, Store &amp;amp; Shop Locator, Directory, Listings &amp;amp; Filters&lt;/p&gt;
&lt;p&gt;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&amp;#39;s permission_callback (can_edit()) only verifies current_user_can(&amp;#39;edit_posts&amp;#39;) 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; tusharimran WP Map Block – Google Maps, OpenStreetMap, Mapbox, Store &amp;amp; Shop Locator, Directory, Listings &amp;amp; Filters&lt;/p&gt;
&lt;p&gt;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&amp;#39;s permission_callback (can_edit()) only verifies current_user_can(&amp;#39;edit_posts&amp;#39;) 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-19798</guid>
    </item>
  </channel>
</rss>
