filamentphp filament up to 3.3.50/4.11.3/5.6.3 recordSelectOptionsQuery Select authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 1.65 |
Summary
A vulnerability, which was classified as problematic, has been found in filamentphp filament up to 3.3.50/4.11.3/5.6.3. Affected by this issue is the function recordSelectOptionsQuery. This manipulation of the argument Select causes authorization.
This vulnerability is registered as CVE-2026-48067. Remote exploitation of the attack is possible. No exploit is available.
It is advisable to upgrade the affected component.
Details
A vulnerability classified as problematic was found in filamentphp filament up to 3.3.50/4.11.3/5.6.3. Affected by this vulnerability is the function recordSelectOptionsQuery. The manipulation of the argument Select with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. As an impact it is known to affect integrity. The summary by CVE is:
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.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-48067 since 05/20/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 3.3.51, 4.11.4 or 5.6.4 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
- 3.3.0
- 3.3.1
- 3.3.2
- 3.3.3
- 3.3.4
- 3.3.5
- 3.3.6
- 3.3.7
- 3.3.8
- 3.3.9
- 3.3.10
- 3.3.11
- 3.3.12
- 3.3.13
- 3.3.14
- 3.3.15
- 3.3.16
- 3.3.17
- 3.3.18
- 3.3.19
- 3.3.20
- 3.3.21
- 3.3.22
- 3.3.23
- 3.3.24
- 3.3.25
- 3.3.26
- 3.3.27
- 3.3.28
- 3.3.29
- 3.3.30
- 3.3.31
- 3.3.32
- 3.3.33
- 3.3.34
- 3.3.35
- 3.3.36
- 3.3.37
- 3.3.38
- 3.3.39
- 3.3.40
- 3.3.41
- 3.3.42
- 3.3.43
- 3.3.44
- 3.3.45
- 3.3.46
- 3.3.47
- 3.3.48
- 3.3.49
- 3.3.50
- 4.11.0
- 4.11.1
- 4.11.2
- 4.11.3
- 5.6.0
- 5.6.1
- 5.6.2
- 5.6.3
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: filament 3.3.51/4.11.4/5.6.4
Timeline
05/20/2026 CVE reserved06/23/2026 Advisory disclosed
06/23/2026 VulDB entry created
06/23/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-7q3w-xqjw-g3cr
Status: Confirmed
CVE: CVE-2026-48067 (🔒)
GCVE (CVE): GCVE-0-2026-48067
GCVE (VulDB): GCVE-100-372835
Entry
Created: 06/23/2026 07:27Changes: 06/23/2026 07:27 (65)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.