# CVE-2026-54179: Laravel Backpack CRUD: SingleBase64Image accepts any base64 payload behind a `data:image` prefix — SVG-with-script lands on the public disk

> An authenticated administrator can upload malicious SVG files with scripts via base64 payloads, leading to stored XSS or code execution.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 31 Aug 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-8hw4-7qjr-3wxg

## What is CVE-2026-54179?

CVE-2026-54179 is a medium-severity vulnerability in Laravel-Backpack CRUD, published on 31 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

backpack/crud provides Create, Read, Update & Delete (CRUD) functions for Backpack, a collection of Laravel packages that help users build custom administration panels. From 6.0.0 until 6.8.14 and 7.0.37, the src/app/Library/Uploaders/SingleBase64Image.php methods SingleBase64Image::uploadFiles and SingleBase64Image::uploadRepeatableFiles, used by image fields through withFiles(), accept any data URI beginning with data:image without validating the declared MIME subtype or decoded bytes, while src/app/Library/Uploaders/Support/FileNameGenerator.php method FileNameGenerator::getExtensionFromFile applies mime_content_type() to the data URI instead of the decoded content. An authenticated administrator can therefore store arbitrary file content under an extensionless filename on the configured disk, which can cause stored cross-site scripting or other unintended behavior when the file is served and accessed. This issue is fixed in version 7.0.38 and 6.8.14.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-54179?

4 open source packages ship an affected version, including backpack/crud.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `backpack/crud` | Packagist | From 6.0.0 | 6.8.14 |
| `backpack/crud` | Packagist | From 6.0.0 | 6.8.14 |
| `backpack/crud` | Packagist | From 7.0.0 | 7.0.38 |
| `backpack/crud` | Packagist | From 7.0.0 | 7.0.38 |

## How do I fix CVE-2026-54179?

Upgrade backpack/crud to a fixed version for your release line: 6.8.14 or 7.0.38.

## Is CVE-2026-54179 being exploited?

There is no known exploitation of CVE-2026-54179 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54179 and fix it if it is affected.

What it is: CVE-2026-54179 is a medium-severity vulnerability in Laravel-Backpack CRUD, published on 31 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-54179 in the wild and no public exploit code.

Affected packages and fixed versions:
- backpack/crud (Packagist): affected from 6.0.0; fixed in 6.8.14
- backpack/crud (Packagist): affected from 6.0.0; fixed in 6.8.14
- backpack/crud (Packagist): affected from 7.0.0; fixed in 7.0.38
- backpack/crud (Packagist): affected from 7.0.0; fixed in 7.0.38

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54179/ (Markdown: https://insights.sbomify.com/CVE-2026-54179/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54179
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54179
- OSV: https://osv.dev/vulnerability/CVE-2026-54179

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54179/
Summaries are generated and may contain mistakes; the official description above is the record.