Discourse up to 2025.12.1/2026.1.0 POST Request dynamically-determined object attributes
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Discourse up to 2025.12.1/2026.1.0. It has been declared as problematic. Affected by this issue is some unknown functionality of the component POST Request Handler. Such manipulation leads to dynamically-determined object attributes. This vulnerability is traded as CVE-2026-28219. The attack may be launched remotely. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Discourse up to 2025.12.1/2026.1.0. It has been rated as problematic. Affected by this issue is some unknown processing of the component POST Request Handler. The manipulation with an unknown input leads to a dynamically-determined object attributes vulnerability. Using CWE to declare the problem leads to CWE-915. The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified. Impacted is integrity. CVE summarizes:
Discourse is an open source discussion platform. Prior to versions 2025.12.2, 2026.1.1, and 2026.2.0, an improper authorization check in the topic management logic allows authenticated users to modify privileged attributes of their topics. By manipulating specific parameters in a PUT or POST request, a regular user can elevate a topic’s status to a site-wide notice or banner, bypassing intended administrative restrictions. Versions 2025.12.2, 2026.1.1, and 2026.2.0 patch the issue. There are no practical workarounds to prevent this behavior other than applying the security patch. Administrators concerned about unauthorized promotions should audit recent changes to site banners and global notices until the fix is deployed.
The advisory is available at github.com. This vulnerability is handled as CVE-2026-28219 since 02/25/2026. The exploitation is known to be easy. The attack may be launched remotely. The technical details are unknown and an exploit is not available.
Upgrading to version 2025.12.2, 2026.1.1 or 2026.2.0 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔒
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: Dynamically-determined object attributesCWE: CWE-915 / CWE-913
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
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 2025.12.2/2026.1.1/2026.2.0
Timeline
02/25/2026 CVE reserved02/27/2026 Advisory disclosed
02/27/2026 VulDB entry created
03/03/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-8v26-9f7h-jc8x
Status: Confirmed
CVE: CVE-2026-28219 (🔒)
GCVE (CVE): GCVE-0-2026-28219
GCVE (VulDB): GCVE-100-348074
Entry
Created: 02/27/2026 07:25Updated: 03/03/2026 12:17
Changes: 02/27/2026 07:25 (68), 03/03/2026 12:17 (12)
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.