CVE-2026-32619 | Discourse up to 2026.1.2/2026.2.1 improper authorization
VulDBArchived Mar 31, 2026✓ Full text saved
A vulnerability labeled as critical has been found in Discourse up to 2026.1.2/2026.2.1 . Affected by this issue is some unknown functionality. Such manipulation leads to improper authorization. This vulnerability is documented as CVE-2026-32619 . The attack can be executed remotely. There is not any exploit available. The affected component should be upgraded.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-354477 · CVE-2026-32619 · GCVE-0-2026-32619
Discourse up to 2026.1.2/2026.2.1 improper authorization
HistoryDiffrelatejsonxmlCTI
CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.0 $0-$5k 2.80+
Summaryinfo
A vulnerability marked as critical has been reported in Discourse up to 2026.1.2/2026.2.1. This affects an unknown part. Performing a manipulation results in improper authorization. This vulnerability is reported as CVE-2026-32619. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.
Detailsinfo
A vulnerability, which was classified as critical, was found in Discourse up to 2026.1.2/2026.2.1. This affects an unknown code. The manipulation with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Discourse is an open-source discussion platform. From versions 2026.1.0-latest to before 2026.1.3, 2026.2.0-latest to before 2026.2.2, and 2026.3.0-latest to before 2026.3.0, users who lost access to a topic (e.g., removed from a private category group) could still interact with polls in that topic, including voting and toggling poll status. No content was exposed, but users could modify poll state in topics they should no longer have access to. This issue has been patched in versions 2026.1.3, 2026.2.2, and 2026.3.0.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-32619 since 03/12/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
Upgrading to version 2026.1.3, 2026.2.2 or 2026.3.0 eliminates this vulnerability.
Productinfo
Type
Chat Software
Name
Discourse
Version
2026.1.0
2026.1.1
2026.1.2
2026.2.0
2026.2.1
License
open-source
Website
Product: https://github.com/discourse/discourse/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
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: 🔍
Exploitinginfo
Class: Improper authorization
CWE: CWE-285 / 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 Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: Discourse 2026.1.3/2026.2.2/2026.3.0
Timelineinfo
03/12/2026 CVE reserved
03/31/2026 +18 days Advisory disclosed
03/31/2026 +0 days VulDB entry created
03/31/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: github.com
Status: Confirmed
CVE: CVE-2026-32619 (🔒)
GCVE (CVE): GCVE-0-2026-32619
GCVE (VulDB): GCVE-100-354477
Entryinfo
Created: 03/31/2026 20:09
Changes: 03/31/2026 20:09 (66)
Complete: 🔍
Cache ID: 99:5F4:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸
Do you want to use VulDB in your project?
Use the official API to access entries easily!