BlackCat CMS 1.2 Backend info.php new_modulename cross-site request forgery

Summaryinfo

A vulnerability labeled as critical has been found in BlackCat CMS 1.2. Affected by this vulnerability is an unknown functionality of the file info.php of the component Backend. Executing a manipulation of the argument new_modulename as part of Parameter can lead to cross-site request forgery. This vulnerability appears as CVE-2017-14048. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability was found in BlackCat CMS 1.2 (Content Management System). It has been declared as critical. This vulnerability affects an unknown part of the file info.php of the component Backend. The manipulation of the argument new_modulename as part of a Parameter leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

BlackCat CMS 1.2 allows remote authenticated users to inject arbitrary PHP code into info.php via a crafted new_modulename parameter to backend/addons/ajax_create.php. NOTE: this can be exploited via CSRF.

The bug was discovered 08/30/2017. The weakness was presented 08/31/2017 (Website). The advisory is available at github.com. This vulnerability was named CVE-2017-14048 since 08/30/2017. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:info.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

See VDB-106020, VDB-106019 and VDB-106016 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Content Management System

Vendor

• BlackCat

Name

• CMS

Version

• 1.2

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion