Pagekit 1.0.17 CSRF Token cross-site request forgery

Summaryinfo

A vulnerability classified as problematic has been found in Pagekit 1.0.17. This affects an unknown part of the component CSRF Token Handler. The manipulation leads to cross-site request forgery. This vulnerability is traded as CVE-2019-19013. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability was found in Pagekit 1.0.17. It has been rated as problematic. This issue affects some unknown processing of the component CSRF Token Handler. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity. The summary by CVE is:

A CSRF vulnerability in Pagekit 1.0.17 allows an attacker to upload an arbitrary file by removing the CSRF token from a request.

The weakness was shared 11/22/2019. The identification of this vulnerability is CVE-2019-19013 since 11/17/2019. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available.

The exploit is available at packetstormsecurity.com. It is declared as proof-of-concept.

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

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

• Pagekit

Version

• 1.0.17

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion