dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-48067

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 →
71/100
Remediation priority · Elevated
Remotely reachable 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 filament/actions 4.0.0 until 4.11.4 and 5.6.4 and from filament/tables 3.0.0 until 3.3.51, the recordSelectOptionsQuery() method may be used to scope the options available in the Select field for AttachAction and AssociateAction. However, the built-in validation rule for these fields did not apply the same scope. As a result, a user who can trigger these actions could tamper with the Livewire component's state and submit an out-of-scope value. This vulnerability is fixed in filament/actions 4.11.4 and 5.6.4 and filament/tables 3.3.51.

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

In Filament (Laravel PHP framework components), the recordSelectOptionsQuery() method scopes available options in Select fields for AttachAction and AssociateAction. However, the built-in validation rule for these fields did not apply the same scope, allowing users who can trigger these actions to tamper with Livewire component state and submit out-of-scope values.

MitigationUpgrade to filament/actions version 4.11.4 or 5.6.4, or filament/tables version 3.3.51 or higher, which apply the same query scope to validation as to the options rendering.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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 package version
    Run `composer show filament/actions` or `composer show filament/tables` to get the installed version number
    Affected if The version is lower than 4.11.4 or 5.6.4 for filament/actions, or lower than 3.3.51 for filament/tables
  2. Check for AttachAction or AssociateAction usage
    Search your codebase for classes extending `AttachAction` or `AssociateAction` that define Select form components
    Affected if These actions with Select fields are in use and the code uses recordSelectOptionsQuery() to scope options
  3. Inspect recordSelectOptionsQuery implementation
    Look for any custom override of the recordSelectOptionsQuery() method in your action classes that applies additional scoping to the query
    Affected if A custom recordSelectOptionsQuery() method exists that filters options but the corresponding validation does not apply the same filter
  4. Verify validation scope matches option scope
    Examine the validation rules applied to the Select field in the action form - check if they use the same query scope as recordSelectOptionsQuery()
    Affected if Validation rules do not replicate the same query conditions that recordSelectOptionsQuery() applies to the options list
  5. Check Livewire component state exposure
    Review if the Select field is configured with `exists` or custom validation rules that bypass the recordSelectOptionsQuery scope
    Affected if Validation allows values outside the scoped options returned by recordSelectOptionsQuery()

You are affected if using filament/actions before 4.11.4/5.6.4 or filament/tables before 3.3.51 with AttachAction or AssociateAction that use custom recordSelectOptionsQuery() scoping, where validation does not apply the same scope to submitted values.

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 to filament/actions version 4.11.4 or 5.6.4, or filament/tables version 3.3.51 or higher, which apply the same query scope to validation as to the options rendering.

Recommended fix High confidence

filament/actions:4.11.4 and filament/tables:3.3.51 (or latest 4.x and 3.x patches)

  1. Run `composer require filament/actions:4.11.4 filament/tables:3.3.51 --no-interaction` to upgrade to the patched versions
  2. Alternatively, run `composer require filament/actions:^4.11 filament/tables:^3.3 --no-interaction` to get the latest patch in each minor series
  3. Verify the installed versions with `composer show filament/actions` and `composer show filament/tables`
  4. Test that AttachAction and AssociateAction properly validate select options against the scoped query

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-48067 — 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-48067 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