<?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://cve.radiocsirt.org</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>Sat, 10 Oct 2026 05:04:38 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-348667</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-348667</link>
      <description>EUVD-2026-348667</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-348667</guid>
    </item>
    <item>
      <title>fkie_cve-2026-8761</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-8761</link>
      <description>&lt;p&gt;The Dokan plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 5.0.1. This is due to a missing authorization check in the `CustomersController` REST controller (`includes/REST/CustomersController.php`), which re-registers WooCommerce&amp;#39;s customer CRUD routes under the `/dokan/v1/customers/` namespace and replaces WooCommerce&amp;#39;s native `manage_woocommerce` capability check with a vendor-only check that inspects the **requesting** user&amp;#39;s role and never validates the **target** user. This makes it possible for authenticated attackers with Vendor/Seller-level access and above to read, modify, or delete any WordPress user — including administrators — via `GET`/`PUT`/`DELETE` requests against `/wp-json/dokan/v1/customers/{id}`. Setting the `password` parameter on an administrator&amp;#39;s record yields a full site takeover.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Dokan plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 5.0.1. This is due to a missing authorization check in the `CustomersController` REST controller (`includes/REST/CustomersController.php`), which re-registers WooCommerce&amp;#39;s customer CRUD routes under the `/dokan/v1/customers/` namespace and replaces WooCommerce&amp;#39;s native `manage_woocommerce` capability check with a vendor-only check that inspects the **requesting** user&amp;#39;s role and never validates the **target** user. This makes it possible for authenticated attackers with Vendor/Seller-level access and above to read, modify, or delete any WordPress user — including administrators — via `GET`/`PUT`/`DELETE` requests against `/wp-json/dokan/v1/customers/{id}`. Setting the `password` parameter on an administrator&amp;#39;s record yields a full site takeover.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-8761</guid>
    </item>
    <item>
      <title>GHSA-q7fj-7hxw-7x69</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q7fj-7hxw-7x69</link>
      <description>&lt;p&gt;The Dokan plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 5.0.1. This is due to a missing authorization check in the `CustomersController` REST controller (`includes/REST/CustomersController.php`), which re-registers WooCommerce&amp;#39;s customer CRUD routes under the `/dokan/v1/customers/` namespace and replaces WooCommerce&amp;#39;s native `manage_woocommerce` capability check with a vendor-only check that inspects the **requesting** user&amp;#39;s role and never validates the **target** user. This makes it possible for authenticated attackers with Vendor/Seller-level access and above to read, modify, or delete any WordPress user — including administrators — via `GET`/`PUT`/`DELETE` requests against `/wp-json/dokan/v1/customers/{id}`. Setting the `password` parameter on an administrator&amp;#39;s record yields a full site takeover.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Dokan plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 5.0.1. This is due to a missing authorization check in the `CustomersController` REST controller (`includes/REST/CustomersController.php`), which re-registers WooCommerce&amp;#39;s customer CRUD routes under the `/dokan/v1/customers/` namespace and replaces WooCommerce&amp;#39;s native `manage_woocommerce` capability check with a vendor-only check that inspects the **requesting** user&amp;#39;s role and never validates the **target** user. This makes it possible for authenticated attackers with Vendor/Seller-level access and above to read, modify, or delete any WordPress user — including administrators — via `GET`/`PUT`/`DELETE` requests against `/wp-json/dokan/v1/customers/{id}`. Setting the `password` parameter on an administrator&amp;#39;s record yields a full site takeover.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q7fj-7hxw-7x69</guid>
    </item>
  </channel>
</rss>
