GHSA-44pg-c29v-hp6r
Laravel Guard bypass in Eloquent models
In laravel releases before 6.18.34 and 7.23.2. It was possible to mass assign Eloquent attributes that included the model's table name:
$model->fill(['users.name' => 'Taylor']);
When doing so, Eloquent would remove the table name from the attribute for you. This was a "convenience" feature of Eloquent and was not documented.
However, when paired with validation, this can lead to unexpected and unvalidated values being saved to the database. For this reason, we have removed the automatic stripping of table names from mass-asignment operations so that the attributes go through the typical "fillable" / "guarded" logic. Any attributes containing table names that are not explicitly declared as fillable will be discarded.
This security release will be a breaking change for applications that were relying on the undocumented table name stripping during mass assignment. Since this feature was relatively unknown and undocumented, we expect the vast majority of Laravel applications to be able to upgrade without issues.
What each source reports
GitHub AdvisoriesNo score
Laravel Guard bypass in Eloquent models
In laravel releases before 6.18.34 and 7.23.2. It was possible to mass assign Eloquent attributes that included the model's table name:
$model->fill(['users.name' => 'Taylor']);
When doing so, Eloquent would remove the table name from the attribute for you. This was a "convenience" feature of Eloquent and was not documented.
However, when paired with validation, this can lead to unexpected and unvalidated values being saved to the database. For this reason, we have removed the automatic stripping of table names from mass-asignment operations so that the attributes go through the typical "fillable" / "guarded" logic. Any attributes containing table names that are not explicitly declared as fillable will be discarded.
This security release will be a breaking change for applications that were relying on the undocumented table name stripping during mass assignment. Since this feature was relatively unknown and undocumented, we expect the vast majority of Laravel applications to be able to upgrade without issues.
- Record
GHSA-44pg-c29v-hp6r- Weakness
- CWE-20
- Updated
- 2026-11-02
OSVNo score
Laravel Guard bypass in Eloquent models
In laravel releases before 6.18.34 and 7.23.2. It was possible to mass assign Eloquent attributes that included the model's table name:
$model->fill(['users.name' => 'Taylor']);
When doing so, Eloquent would remove the table name from the attribute for you. This was a "convenience" feature of Eloquent and was not documented.
However, when paired with validation, this can lead to unexpected and unvalidated values being saved to the database. For this reason, we have removed the automatic stripping of table names from mass-asignment operations so that the attributes go through the typical "fillable" / "guarded" logic. Any attributes containing table names that are not explicitly declared as fillable will be discarded.
This security release will be a breaking change for applications that were relying on the undocumented table name stripping during mass assignment. Since this feature was relatively unknown and undocumented, we expect the vast majority of Laravel applications to be able to upgrade without issues.
- Record
GHSA-44pg-c29v-hp6r- Weakness
- CWE-20
- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
laravel/frameworkPackagist | 5.5.0 to 5.5.49 | None known |
laravel/frameworkPackagist | 6.0.0 up to 6.18.34 | 6.18.34 |
laravel/frameworkPackagist | 7.0.0 up to 7.23.2 | 7.23.2 |
laravel/frameworkPackagist | 5.5.0 to 5.5.49, plus listed versions v5.5.0v5.5.1v5.5.10v5.5.11v5.5.12 Show 45 moreShow lessv5.5.13v5.5.14v5.5.15v5.5.16v5.5.17v5.5.18v5.5.19v5.5.2v5.5.20v5.5.21v5.5.22v5.5.23v5.5.24v5.5.25v5.5.26v5.5.27v5.5.28v5.5.29v5.5.3v5.5.30v5.5.31v5.5.32v5.5.33v5.5.34v5.5.35v5.5.36v5.5.37v5.5.38v5.5.39v5.5.4v5.5.40v5.5.41v5.5.42v5.5.43v5.5.44v5.5.45v5.5.46v5.5.47v5.5.48v5.5.49v5.5.5v5.5.6v5.5.7v5.5.8v5.5.9 | None known |
laravel/frameworkPackagist | 6.0.0 up to 6.18.34, plus listed versions v6.0.0v6.0.1v6.0.2v6.0.3v6.0.4 Show 45 moreShow lessv6.1.0v6.10.0v6.10.1v6.11.0v6.12.0v6.13.0v6.13.1v6.14.0v6.15.0v6.15.1v6.16.0v6.17.0v6.17.1v6.18.0v6.18.1v6.18.10v6.18.11v6.18.12v6.18.13v6.18.14v6.18.15v6.18.16v6.18.17v6.18.18v6.18.19v6.18.2v6.18.20v6.18.21v6.18.22v6.18.23v6.18.24v6.18.25v6.18.26v6.18.27v6.18.28v6.18.29v6.18.3v6.18.30v6.18.31v6.18.32v6.18.33v6.18.4v6.18.5v6.18.6v6.18.7 | 6.18.34 |
laravel/frameworkPackagist | 7.0.0 up to 7.23.2, plus listed versions v7.0.0v7.0.1v7.0.2v7.0.3v7.0.4 Show 45 moreShow lessv7.0.5v7.0.6v7.0.7v7.0.8v7.1.0v7.1.1v7.1.2v7.1.3v7.10.0v7.10.1v7.10.2v7.10.3v7.11.0v7.12.0v7.13.0v7.14.0v7.14.1v7.15.0v7.16.0v7.16.1v7.17.0v7.17.1v7.17.2v7.18.0v7.19.0v7.19.1v7.2.0v7.2.1v7.2.2v7.20.0v7.21.0v7.22.0v7.22.1v7.22.2v7.22.3v7.22.4v7.23.0v7.23.1v7.3.0v7.4.0v7.5.0v7.5.1v7.5.2v7.6.0v7.6.1 | 7.23.2 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-44pg-c29v-hp6r is a vulnerability with no CVSS score yet in laravel/framework, published May 15, 2024. No source lists public exploit code. Fixed in laravel/framework 6.18.34.
References
Left out here: 23 versions. The JSON record has them.