dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-48500

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Filament is a collection of full-stack components for accelerated Laravel development. From 3.0.0 until 3.3.52, 4.11.5, and 5.6.5, any schema can contain a file upload form field, so Filament applies Livewire's WithFileUploads trait to the Livewire component the schema is embedded in. However, some schemas, such as the panel login form, do not require file uploads, and exposing unauthenticated temporary file uploads on these components is not an acceptable risk. On these components, an unauthenticated attacker could upload arbitrary files to the application's temporary storage, which could be abused to exhaust disk space or inflate storage costs. This vulnerability is fixed in 3.3.52, 4.11.5, and 5.6.5.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Filament applies Livewire's WithFileUploads trait to all components containing file upload form fields, but this trait is also incorrectly applied to schemas like login forms that don't require file uploads, allowing unauthenticated attackers to upload arbitrary files to temporary storage.

MitigationUpgrade Filament to version 3.3.52, 4.11.5, or 5.6.5 or later to receive the patch that prevents unnecessary file upload trait application.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Filament version
    Check your composer.json or run 'composer show filament/filament' to see the installed version
    Affected if version is below 3.3.52, 4.11.5, or 5.6.5 (or if you cannot determine version)
  2. Locate components with file upload fields
    Search codebase for usage of FileUpload::class, Upload::class, or similar upload field types in your Filament resources/pages
    Affected if any component contains file upload fields and Filament version is vulnerable
  3. Identify components that don't require uploads
    Review components found in step 2 and check if they are login forms, auth forms, or other non-file-upload forms that still have upload capability
    Affected if any non-file-upload form (like login) includes an upload field or the trait is applied to it
  4. Inspect temporary upload directory
    Check the system temp directory (e.g., /tmp/filament or storage/framework/cache) for unexpected uploaded files
    Affected if unexpected or unknown files exist in temp directories that correspond to upload timestamps

If Filament version is below 3.3.52/4.11.5/5.6.5 AND your application has any components with file upload fields, the unnecessary WithFileUploads trait may be applied and the environment could be affected.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Filament to version 3.3.52, 4.11.5, or 5.6.5 or later to receive the patch that prevents unnecessary file upload trait application.

Recommended fix High confidence

Upgrade to Filament 3.3.52 (branch 3.x), 4.11.5 (branch 4.x), or 5.6.5 (branch 5.x)

  1. Identify the Filament branch currently in use (3.x, 4.x, or 5.x) by checking the composer.json or lock file
  2. Run 'composer require filament/filament:^3.3.52' for branch 3.x, 'composer require filament/filament:^4.11.5' for branch 4.x, or 'composer require filament/filament:^5.6.5' for branch 5.x
  3. Run 'composer update filament/filament --with-all-dependencies' to apply the upgrade
  4. Verify the upgrade was successful by running 'composer show filament/filament' and confirming the version number
  5. Clear any cached configurations with 'php artisan clear-compiled' or 'php artisan config:clear'

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48500 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48500 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data