EUVD-2026-324439

fkie_cve-2022-31114

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()`.

GHSA-m8xx-3x29-84h8 — backpack/crud is vulnerable to Cross-Site Scripting (XSS)

Affected: Packagist: backpack/crud

### Impact

It’s a “*moderate*” vulnerability… but being an admin panel, take this seriously. It’s difficult… but an attacker could conduct a targeted phishing campaign, in order to **trick your users or admins to click a malicious link, which under very specific circumstances could give them information... or even admin access**. It’s *unlikely*, but that’s not good enough in admin panels - It should be made *impossible*. That’s why you are bothered with this.

### Patches

If you don’t have custom error views, the views provided by Backpack would output the exception message *without escaping it*, which made an attack possible using Reflected XSS, in some very specific circumstances (that we will not disclose). **To fix those error views in Backpack 4.x and 5.x, please run**:

```bash composer update backpack/crud php artisan backpack:fix ```

The problem has been patched in: - v4.0.63 - v4.1.69 - v5.0.13

> **IMPORTANT! Running a `composer update` should get you the patched version, but you also need to run `php artisan backpack:fix` afterwards, to patch your published error views, if necessary.**

### Workarounds

Alternatively (if you don’t want to run `composer update`), you can manually look inside your error views in “*resources/views/errors*” and output `e($exception->getMessage())` instead of `$exception->getMessage()`. That’s all there is to the fix, really.

### What the maintainers have done about this

Acted as soon as our team found it (last week of March 20…

Most recent entries from all

EUVD-2026-324439

fkie_cve-2022-31114

GHSA-m8xx-3x29-84h8 — backpack/crud is vulnerable to Cross-Site Scripting (XSS)

gsd-2022-31114