Laravel-Backpack CRUD up to 4.0.62/4.1.68/5.0.12 getMessage cross site scripting

Summaryinfo

A vulnerability has been found in Laravel-Backpack CRUD up to 4.0.62/4.1.68/5.0.12 and classified as problematic. Affected is the function getMessage. The manipulation leads to cross site scripting. This vulnerability is uniquely identified as CVE-2022-31114. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Laravel-Backpack CRUD up to 4.0.62/4.1.68/5.0.12. This issue affects the function getMessage. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity. The summary by CVE is:

backpack/crud provides Create, Read, Update & Delete (CRUD) functions for Backpack, a collection of Laravel packages that help users build custom administration panels. Versions prior to 5.0.13, 4.1.69, and 4.0.63 are vulnerable to cross-site scripting. An attacker could conduct a targeted phishing campaign, in order to trick users or admins into clicking a malicious link, which under very specific circumstances could give them information or possibly admin access. Versions 5.0.13, 4.1.69, and 4.0.63 patch the issue. As a workaround, manually look inside error views in `resources/views/errors` and output `e($exception->getMessage())` instead of `$exception->getMessage()`.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2022-31114 since 05/18/2022. The exploitation is known to be easy. 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 of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.

Upgrading to version 4.0.63, 4.1.69 or 5.0.13 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-55999). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Laravel-Backpack

Name

• CRUD

Version

• 4.0.0
• 4.0.1
• 4.0.2
• 4.0.3
• 4.0.4
• 4.0.5
• 4.0.6
• 4.0.7
• 4.0.8
• 4.0.9
• 4.0.10
• 4.0.11
• 4.0.12
• 4.0.13
• 4.0.14
• 4.0.15
• 4.0.16
• 4.0.17
• 4.0.18
• 4.0.19
• 4.0.20
• 4.0.21
• 4.0.22
• 4.0.23
• 4.0.24
• 4.0.25
• 4.0.26
• 4.0.27
• 4.0.28
• 4.0.29
• 4.0.30
• 4.0.31
• 4.0.32
• 4.0.33
• 4.0.34
• 4.0.35
• 4.0.36
• 4.0.37
• 4.0.38
• 4.0.39
• 4.0.40
• 4.0.41
• 4.0.42
• 4.0.43
• 4.0.44
• 4.0.45
• 4.0.46
• 4.0.47
• 4.0.48
• 4.0.49
• 4.0.50
• 4.0.51
• 4.0.52
• 4.0.53
• 4.0.54
• 4.0.55
• 4.0.56
• 4.0.57
• 4.0.58
• 4.0.59
• 4.0.60
• 4.0.61
• 4.0.62
• 4.1.0
• 4.1.1
• 4.1.2
• 4.1.3
• 4.1.4
• 4.1.5
• 4.1.6
• 4.1.7
• 4.1.8
• 4.1.9
• 4.1.10
• 4.1.11
• 4.1.12
• 4.1.13
• 4.1.14
• 4.1.15
• 4.1.16
• 4.1.17
• 4.1.18
• 4.1.19
• 4.1.20
• 4.1.21
• 4.1.22
• 4.1.23
• 4.1.24
• 4.1.25
• 4.1.26
• 4.1.27
• 4.1.28
• 4.1.29
• 4.1.30
• 4.1.31
• 4.1.32
• 4.1.33
• 4.1.34
• 4.1.35
• 4.1.36
• 4.1.37
• 4.1.38
• 4.1.39
• 4.1.40
• 4.1.41
• 4.1.42
• 4.1.43
• 4.1.44
• 4.1.45
• 4.1.46
• 4.1.47
• 4.1.48
• 4.1.49
• 4.1.50
• 4.1.51
• 4.1.52
• 4.1.53
• 4.1.54
• 4.1.55
• 4.1.56
• 4.1.57
• 4.1.58
• 4.1.59
• 4.1.60
• 4.1.61
• 4.1.62
• 4.1.63
• 4.1.64
• 4.1.65
• 4.1.66
• 4.1.67
• 4.1.68
• 5.0.0
• 5.0.1
• 5.0.2
• 5.0.3
• 5.0.4
• 5.0.5
• 5.0.6
• 5.0.7
• 5.0.8
• 5.0.9
• 5.0.10
• 5.0.11
• 5.0.12

Website

• Product: https://github.com/Laravel-Backpack/CRUD/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion