Django CMS up to 3.0.13/3.1.0 cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Django CMS up to 3.0.13/3.1.0. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in cross-site request forgery. This vulnerability is identified as CVE-2015-5081. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Django CMS up to 3.0.13/3.1.0 (Content Management System). This affects an unknown code. The manipulation 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 summary by CVE is:
Cross-site request forgery (CSRF) vulnerability in django CMS before 3.0.14, 3.1.x before 3.1.1 allows remote attackers to manipulate privileged users into performing unknown actions via unspecified vectors.
The bug was discovered 06/27/2015. The weakness was released 08/18/2017 (oss-sec). The advisory is shared at openwall.com. This vulnerability is uniquely identified as CVE-2015-5081 since 06/26/2015. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 783 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 3.0.14 or 3.1.1 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
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 3.0.14/3.1.1
Patch: github.com
Timeline
06/26/2015 🔍06/27/2015 🔍
08/18/2017 🔍
08/18/2017 🔍
08/19/2017 🔍
12/16/2022 🔍
Sources
Advisory: f77cbc607d6e2a62e63287d37ad320109a2cc78aStatus: Not defined
Confirmation: 🔍
CVE: CVE-2015-5081 (🔍)
GCVE (CVE): GCVE-0-2015-5081
GCVE (VulDB): GCVE-100-105501
Entry
Created: 08/19/2017 08:40Updated: 12/16/2022 08:39
Changes: 08/19/2017 08:40 (59), 11/08/2019 15:09 (1), 12/16/2022 08:39 (5)
Complete: 🔍
Cache ID: 216:485:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.