AI Science Tracker

Discourse topic moves can bypass destination-category visibility checks

Discourse topic and message category-move authorization · AI involvement attributed to Anthropic OSS Scanner (model not identified for this finding)

Finding and attribution

The project’s security fix makes topic moves into a destination category require that the user can see that category. The change applies to moderators and members, and also to converting a message to a public topic or changing a queued topic category; existing admin and moderator exceptions for visible categories are preserved. The source does not detail a particular data exposure or attacker scenario, so impact is limited here to the authorization boundary bypass described by the maintainers.

Product: Discourse topic and message category-move authorization. AI system: Anthropic OSS Scanner (model not identified for this finding). Team / organization: Anthropic and Discourse maintainers.

CVE identifiers: Not established in the cited evidence.

AI and human contribution (source account): The official Discourse release changelog identifies the main security change (#45852, backported as #45854) as discovered by Anthropic OSS Scanner under ANT-2026-ADPDEAPP. Anthropic’s scanner documentation says its fast-track reports are generated directly by its strongest models; the specific model/version is not identified.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The project classifies the change as a security fix and explicitly credits Anthropic OSS Scanner. No CVE/GHSA is named in the reviewed primary sources; the original pull request #45852 is the public issue identifier. No exploitation claim is made.

Remediation status: fix documented. Category changes now require the user to see the destination category across direct topic moves, message-to-topic conversion, and queued-topic edits, while preserving documented admin/moderator permissions for categories they can see. The change was backported to releases 2026.10 (#45854), 2026.9 (#45855), and 2026.7 (#45856). Deployed patch status is not checked.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 6 Nov 2026. AI attribution dated 6 Nov 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Not available · no assessment established here. Documented technical effects: other.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

No source-backed CVSS assessment is established in this catalog.

Case-level evidence: other.
Prerequisites / affected scope: The fix addresses a visibility authorization bypass in the affected Discourse behavior; it does not establish that protected data was actually disclosed..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.

Documented fix: Category changes now require the user to see the destination category across direct topic moves, message-to-topic conversion, and queued-topic edits, while preserving documented admin/moderator permissions for categories they can see. The change was backported to releases 2026.10 (#45854), 2026.9 (#45855), and 2026.7 (#45856). Deployed patch status is not checked.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases