<?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>Thu, 15 Oct 2026 20:45:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-33650 — AVideo's Video Moderator Privilege Escalation via Ownership Transfer Enables Arbitrary Video Deletion</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-33650</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; WWBN AVideo&lt;/p&gt;
&lt;p&gt;WWBN AVideo is an open source video platform. In versions up to and including 26.0, a user with the &amp;#34;Videos Moderator&amp;#34; permission can escalate privileges to perform full video management operations — including ownership transfer and deletion of any video — despite the permission being documented as only allowing video publicity changes (Active, Inactive, Unlisted). The root cause is that `Permissions::canModerateVideos()` is used as an authorization gate for full video editing in `videoAddNew.json.php`, while `videoDelete.json.php` only checks ownership, creating an asymmetric authorization boundary exploitable via a two-step ownership-transfer-then-delete chain. Commit 838e16818c793779406ecbf34ebaeba9830e33f8 contains a patch.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; WWBN AVideo&lt;/p&gt;
&lt;p&gt;WWBN AVideo is an open source video platform. In versions up to and including 26.0, a user with the &amp;#34;Videos Moderator&amp;#34; permission can escalate privileges to perform full video management operations — including ownership transfer and deletion of any video — despite the permission being documented as only allowing video publicity changes (Active, Inactive, Unlisted). The root cause is that `Permissions::canModerateVideos()` is used as an authorization gate for full video editing in `videoAddNew.json.php`, while `videoDelete.json.php` only checks ownership, creating an asymmetric authorization boundary exploitable via a two-step ownership-transfer-then-delete chain. Commit 838e16818c793779406ecbf34ebaeba9830e33f8 contains a patch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-33650</guid>
    </item>
  </channel>
</rss>
