CVE-2026-54179: XSS
Summary
SingleBase64Image::uploadFiles — the uploader bound to image-typed fields via withFiles() — only verifies that the submitted value starts with the string data:image. The MIME subtype and the base64-decoded bytes are never inspected or validated. A related bug in FileNameGenerator causes the stored file to receive an extensionless filename, because mimecontenttype() returns false when given a data URI instead of a filesystem path.
The combination allows an authenticated admin to store a file of arbitrary type on the configured disk under a name without a recognizable extension.
Details
php // src/app/Library/Uploaders/SingleBase64Image.php if (Str::startsWith($value, 'data:image')) { // MIME subtype and decoded bytes are not validated $base64Image = Str::after($value, ';base64,'); $finalPath = $this->getPath() . $this->getFileName($value); Storage::disk($this->getDisk())->put($finalPath, base64decode($base64Image)); return $finalPath; }
// src/app/Library/Uploaders/Support/FileNameGenerator.php private function getExtensionFromFile(string|UploadedFile $file): string { return isa($file, UploadedFile::class, true) ? $file->extension() : Str::after(mimecontenttype($file), '/'); // returns false on data URIs → empty string }
The stored filename ends with a trailing dot and no extension.
Impact
An authenticated admin submitting a malicious payload to a Backpack image field stored with withFiles() can write arbitrary file content to the configured storage disk. Depending on server configuration and how stored files are served, this may lead to stored XSS or other unintended behavior when the file is later accessed.
Fix
The fix validates the declared MIME subtype against an allowlist, decodes the base64 payload, and verifies the actual file bytes with finfo before storing. The extension is derived from the detected MIME type rather than the data URI string. Applied in SingleBase64Image::uploadFiles and uploadRepeatableFiles; FileNameGenerator::getExtensionFromFile now rejects inputs that produce an empty extension.
Setting X-Content-Type-Options: nosniff on admin responses is a useful defense-in-depth complement.
Affected versions
- >= 6.0.0, < 6.8.14 - >= 7.0.0, < 7.0.38
Patched versions
- 6.8.14 - 7.0.38
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/backpack/crudto a version that resolves this vulnerability.Fixed in 7.0.38 - Upgrade
Upgrade
composer/backpack/crudto a version that resolves this vulnerability.Fixed in 6.8.14 - Upgrade
Upgrade
Backpack SingleBase64Image uploaderto a version that resolves this vulnerability.Fixed in 6.8.14 - Upgrade
Upgrade
Backpack SingleBase64Image uploaderto a version that resolves this vulnerability.Fixed in 7.0.38 - Configuration
Set header X-Content-Type-Options: nosniff on admin responses as defense-in-depth complement.
HTTP responses (admin) X-Content-Type-Options = nosniff
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated administrator who can submit values to an image-typed field bound through withFiles() can exploit it. The affected upload path is SingleBase64Image::uploadFiles.
What does an attacker need to provide?
The submitted value only needs to begin with data:image. The MIME subtype and base64-decoded content are not validated, allowing arbitrary decoded file content to be stored.
Where are uploaded files written, and how are they named?
Files are written to the configured storage disk. Due to the filename-generation issue, files uploaded through this path receive extensionless names.
How can we assess whether our application uses the affected path?
Review image-typed fields configured with withFiles() and determine whether they use SingleBase64Image::uploadFiles. Also review the configured disk for extensionless files created through image upload workflows.
Which release references are provided for remediation review?
The provided references include Backpack CRUD releases 6.8.14 and 7.0.38. Review those release notes and the linked advisory when planning an update.