<?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>Fri, 20 Nov 2026 12:57:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-130055 — VidShop &lt;= 1.10.0 - Missing Authorization to Unauthenticated Hidden Product Data Disclosure via '/vsfw/v1/products/{id}…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-130055</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; wpcreatix VidShop – Shoppable Videos for WooCommerce&lt;/p&gt;
&lt;p&gt;The VidShop for WooCommerce plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 1.10.0 via the /vsfw/v1/products/{id} REST API endpoint. This is due to the endpoint&amp;#39;s permission_callback (check_public_permission) returning true unconditionally and the get_item() handler only checking that the product and video exist — it does not check the product&amp;#39;s post_status or catalog visibility, nor does it verify that the product is actually linked to the supplied video_id. This makes it possible for unauthenticated attackers to enumerate product IDs and read private, draft, and catalog-hidden WooCommerce products&amp;#39; names, short descriptions, prices, variations, attributes, and stock information that would otherwise be hidden from public view.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; wpcreatix VidShop – Shoppable Videos for WooCommerce&lt;/p&gt;
&lt;p&gt;The VidShop for WooCommerce plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 1.10.0 via the /vsfw/v1/products/{id} REST API endpoint. This is due to the endpoint&amp;#39;s permission_callback (check_public_permission) returning true unconditionally and the get_item() handler only checking that the product and video exist — it does not check the product&amp;#39;s post_status or catalog visibility, nor does it verify that the product is actually linked to the supplied video_id. This makes it possible for unauthenticated attackers to enumerate product IDs and read private, draft, and catalog-hidden WooCommerce products&amp;#39; names, short descriptions, prices, variations, attributes, and stock information that would otherwise be hidden from public view.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-130055</guid>
    </item>
  </channel>
</rss>
