Coop has cross-org IDOR in addAccessibleQueuesForUser / removeAccessibleQueuesForUser
Coop versions before 1.0.2 are affected. The fix is in 1.0.2.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.0.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Coop, an open source content review and moderation tool from ROOST, is affected. An authenticated user in one organization with queue-edit permission could grant or revoke manual review queue access for users in a different organization, letting them change who can see and work those queues, though they could not read the other organization's queues or data.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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's users' access to manual review queues. The existing queue-edit permission check did not bind the supplied identifiers to the caller's organization. The attacker could not read the other organization's queues or jobs, so this issue did not disclose confidential data. This issue is fixed in version 1.0.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- roostorg coop
fixed in 1.0.2
References 4
GitHub · roostorg/coop
Questions about CVE-2026-63401
What does this mean?
An authenticated user can grant or revoke another organization's users' access to that organization's manual review queues through the addAccessibleQueuesForUser and removeAccessibleQueuesForUser functions.Source: github.com
Am I affected, and how do I check?
Coop versions before 1.0.2 are affected. To check a Coop installation, look at its installed version.Source: github.com
What should I do about it?
Upgrade Coop to version 1.0.2, which is the patched release.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data