Concrete CMS up to 8.5.5 Calendar save ccm_token cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Concrete CMS up to 8.5.5. It has been rated as problematic. Affected by this issue is some unknown functionality of the file ccm/calendar/dialogs/event/add/save of the component Calendar. Performing a manipulation of the argument ccm_token results in cross-site request forgery. This vulnerability was named CVE-2021-40108. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic has been found in Concrete CMS up to 8.5.5 (Content Management System). This affects an unknown function of the file ccm/calendar/dialogs/event/add/save of the component Calendar. The manipulation of the argument ccm_token with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity.
The weakness was presented 09/27/2021. The advisory is shared at hackerone.com. This vulnerability is uniquely identified as CVE-2021-40108 since 08/25/2021. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
Upgrading to version 8.5.6 eliminates this vulnerability. The upgrade is hosted for download at documentation.concretecms.org.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.1VulDB Meta Temp Score: 6.1
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
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: CMS 8.5.6
Timeline
08/25/2021 🔍09/27/2021 🔍
09/27/2021 🔍
10/02/2021 🔍
Sources
Advisory: hackerone.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2021-40108 (🔍)
GCVE (CVE): GCVE-0-2021-40108
GCVE (VulDB): GCVE-100-183393
Entry
Created: 09/27/2021 17:36Updated: 10/02/2021 17:24
Changes: 09/27/2021 17:36 (45), 10/02/2021 17:16 (1), 10/02/2021 17:24 (18)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.