<?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>Mon, 02 Nov 2026 23:11:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-63401 — Coop has cross-org IDOR in addAccessibleQueuesForUser / removeAccessibleQueuesForUser</title>
      <link>https://db.gcve.eu/vuln/cve-2026-63401</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; roostorg coop&lt;/p&gt;
&lt;p&gt;Coop is an open source review and moderation tool from ROOST. Prior to 1.0.2, `addAccessibleQueuesForUser` and `removeAccessibleQueuesForUser` accepted arbitrary `queueId` and `userId` values without organization scoping. An authenticated user belonging to one organization and holding MRT queue-edit permission could grant or revoke another organization&amp;#39;s users&amp;#39; access to manual review queues. The existing queue-edit permission check did not bind the supplied identifiers to the caller&amp;#39;s organization. The attacker could not read the other organization&amp;#39;s queues or jobs, so this issue did not disclose confidential data. This issue is fixed in version 1.0.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; roostorg coop&lt;/p&gt;
&lt;p&gt;Coop is an open source review and moderation tool from ROOST. Prior to 1.0.2, `addAccessibleQueuesForUser` and `removeAccessibleQueuesForUser` accepted arbitrary `queueId` and `userId` values without organization scoping. An authenticated user belonging to one organization and holding MRT queue-edit permission could grant or revoke another organization&amp;#39;s users&amp;#39; access to manual review queues. The existing queue-edit permission check did not bind the supplied identifiers to the caller&amp;#39;s organization. The attacker could not read the other organization&amp;#39;s queues or jobs, so this issue did not disclose confidential data. This issue is fixed in version 1.0.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-63401</guid>
    </item>
  </channel>
</rss>
