Discourse up to 2026.1.5/2026.5.1/2026.6.0 privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 1.34- |
Summary
A vulnerability labeled as problematic has been found in Discourse up to 2026.1.5/2026.5.1/2026.6.0. This issue affects the function TopicLink.extract_from/TopicLink.ensure_entry_for/TopicLink.duplicate_lookup. Executing a manipulation can lead to privileges management.
The identification of this vulnerability is CVE-2026-72722. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability was found in Discourse up to 2026.1.5/2026.5.1/2026.6.0. It has been declared as problematic. This vulnerability affects the function TopicLink.extract_from/TopicLink.ensure_entry_for/TopicLink.duplicate_lookup. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality. CVE summarizes:
Discourse is an open-source discussion platform. Prior to 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0, TopicLink.extract_from, TopicLink.ensure_entry_for, and TopicLink.duplicate_lookup do not consistently enforce Guardian.can_see? checks when processing internal links. An authenticated user can submit links to restricted topics, private messages, or hidden posts and receive canonicalized slugs or titles in the composer_messages duplicate_lookup response even though the targets are not visible to that user. This issue is fixed in versions 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0.
The advisory is available at github.com. This vulnerability was named CVE-2026-72722 since 08/10/2026. The exploitation appears to be easy. The attack can be initiated remotely. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
Upgrading to version 2026.1.6, 2026.5.2, 2026.6.1 or 2026.7.0 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
- 2026.0
- 2026.1
- 2026.1.0
- 2026.1.1
- 2026.1.2
- 2026.1.3
- 2026.1.4
- 2026.1.5
- 2026.2
- 2026.3
- 2026.4
- 2026.5
- 2026.5.0
- 2026.5.1
- 2026.6.0
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Discourse 2026.1.6/2026.5.2/2026.6.1/2026.7.0
Timeline
08/10/2026 Advisory disclosed08/10/2026 CVE reserved
08/10/2026 VulDB entry created
08/10/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-72722 (🔒)
GCVE (CVE): GCVE-0-2026-72722
GCVE (VulDB): GCVE-100-387754
Entry
Created: 08/10/2026 18:24Changes: 08/10/2026 18:24 (55)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.