LFCMS 3.7.0 admin.php s cross-site request forgery

Summaryinfo

A vulnerability, which was classified as problematic, has been found in LFCMS 3.7.0. This affects an unknown part of the file admin.php. This manipulation of the argument s as part of Parameter causes cross-site request forgery. The identification of this vulnerability is CVE-2018-12603. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability was found in LFCMS 3.7.0. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file admin.php. The manipulation of the argument s 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 integrity. The summary by CVE is:

Cross-site request forgery (CSRF) vulnerability in admin.php in LFCMS 3.7.0 allows remote attackers to hijack the authentication of unspecified users for requests that add administrator users via the s parameter, a related issue to CVE-2018-12114.

The bug was discovered 06/20/2018. The weakness was shared 06/25/2018 as EDB-ID 44919 as not defined exploit (Exploit-DB). The advisory is shared at exploit-db.com. This vulnerability is known as CVE-2018-12603 since 06/20/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.

After immediately, there has been an exploit disclosed. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:admin.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.

The vulnerability is also documented in the vulnerability database at Exploit-DB (44919). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• LFCMS

Version

• 3.7.0

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion