Discourse discourse-calendar Private Event authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Discourse discourse-calendar. This issue affects some unknown processing of the component Private Event Handler. Executing a manipulation can lead to authorization. The identification of this vulnerability is CVE-2024-26145. The attack may be launched remotely. There is no exploit available. A patch should be applied to remediate this issue.
Details
A vulnerability has been found in Discourse discourse-calendar (Calendar Software) (unknown version) and classified as problematic. This vulnerability affects an unknown code block of the component Private Event Handler. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. As an impact it is known to affect confidentiality. CVE summarizes:
Discourse Calendar adds the ability to create a dynamic calendar in the first post of a topic on Discourse. Uninvited users are able to gain access to private events by crafting a request to update their attendance. This problem is resolved in commit dfc4fa15f340189f177a1d1ab2cc94ffed3c1190. As a workaround, one may use post visibility to limit access.
The weakness was shared 02/21/2024. The advisory is available at github.com. This vulnerability was named CVE-2024-26145 since 02/14/2024. The technical details are unknown and an exploit is not available.
Applying the patch dfc4fa15f340189f177a1d1ab2cc94ffed3c1190 is able to eliminate this problem.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 5.0
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔍
CNA Base Score: 6.5
CNA Vector (GitHub, Inc.): 🔍
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: AuthorizationCWE: CWE-863 / CWE-285 / CWE-266
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: dfc4fa15f340189f177a1d1ab2cc94ffed3c1190
Timeline
02/14/2024 🔍02/21/2024 🔍
02/21/2024 🔍
02/06/2025 🔍
Sources
Product: github.comAdvisory: dfc4fa15f340189f177a1d1ab2cc94ffed3c1190
Status: Confirmed
CVE: CVE-2024-26145 (🔍)
GCVE (CVE): GCVE-0-2024-26145
GCVE (VulDB): GCVE-100-254434
Entry
Created: 02/21/2024 19:13Updated: 02/06/2025 10:12
Changes: 02/21/2024 19:13 (48), 03/13/2024 09:52 (2), 03/13/2024 09:56 (1), 02/06/2025 10:12 (27)
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.