Answer in brief
CVE-2026-54179 records a Medium severity (CVSS 4.4) vulnerability in backpack/crud: SingleBase64Image accepts any base64 payload behind a `data:image` prefix — SVG-with-script lands on the public disk. The current sources do not mark it as known exploited. The current feed maps backpack/crud (composer), backpack/crud (composer), Laravel-Backpack/CRUD (generic), backpack/crud (packagist) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps backpack/crud (composer), backpack/crud (composer), Laravel-Backpack/CRUD (generic), backpack/crud (packagist) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| backpack/crudcomposer | >=6.0.0,<6.8.14 | 6.8.14 |
| backpack/crudcomposer | >=7.0.0,<7.0.38 | 7.0.38 |
| Laravel-Backpack/CRUDgeneric | >= 6.0.0, < 6.8.14 || >= 7.0.0, < 7.0.38 | Not reported |
| backpack/crudpackagist | >=6.0.0 <6.8.14 | 6.8.14 |
| backpack/crudpackagist | >=7.0.0 <7.0.38 | 7.0.38 |
Published upstream
Aug 31, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 31, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 20, 2026
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.
Quoted source text, attributed separately from HOL analysis.