DotClear up to 2.10 admin/media.php upfiletitle/media_title cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in DotClear up to 2.10. This issue affects some unknown processing of the file admin/media.php. Performing a manipulation of the argument upfiletitle/media_title results in cross site scripting. This vulnerability is known as CVE-2016-9891. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in DotClear up to 2.10 (Blog Software). This affects an unknown functionality of the file admin/media.php. The manipulation of the argument upfiletitle/media_title with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:
Cross-site scripting (XSS) vulnerability in admin/media.php and admin/media_item.php in Dotclear before 2.11 allows remote authenticated users to inject arbitrary web script or HTML via the upfiletitle or media_title parameter (aka the media title).
The bug was discovered 12/29/2016. The weakness was published 12/29/2016 (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2016-9891 since 12/07/2016. It is possible to initiate the attack remotely. The successful exploitation needs a authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
By approaching the search of inurl:admin/media.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.11 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 95156†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
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 scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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: DotClear 2.11
Timeline
12/07/2016 🔍12/29/2016 🔍
12/29/2016 🔍
12/29/2016 🔍
12/29/2016 🔍
12/30/2016 🔍
10/13/2022 🔍
Sources
Advisory: 5536⛔Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-9891 (🔍)
GCVE (CVE): GCVE-0-2016-9891
GCVE (VulDB): GCVE-100-94725
SecurityFocus: 95156 - Dotclear CVE-2016-9891 Multiple Cross Site Scripting Vulnerabilities
Entry
Created: 12/30/2016 10:29Updated: 10/13/2022 00:50
Changes: 12/30/2016 10:29 (58), 07/22/2019 07:30 (6), 10/13/2022 00:50 (3)
Complete: 🔍
Cache ID: 216::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.