GHSA-4mg9-vhxq-vm7j — laravel/framework
GHSA-4mg9-vhxq-vm7j is a security vulnerability in laravel/framework. A fix is available for laravel/framework — see the affected versions and patch details below.
SQL Server LIMIT / OFFSET SQL Injection in laravel/framework and illuminate/database
Real-World Exposure
laravel/framework🐘laravel/framework🐘illuminate/database🐘illuminate/databaseReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Those using SQL Server with Laravel and allowing user input to be passed directly to the limit and offset functions are vulnerable to SQL injection. Other database drivers such as MySQL and Postgres are not affected by this vulnerability.
Patches
This problem has been patched on Laravel versions 6.20.26, 7.30.5, and 8.40.0.
Workarounds
You may workaround this vulnerability by ensuring that only integers are passed to the limit and offset functions, as well as the skip and take functions.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | laravel/framework | ≥ 8.0.0&&< 8.40.0 | 8.40.0composer require laravel/framework:^8.40.0 |
| 🐘Packagist | laravel/framework | all versions | 6.20.26composer require laravel/framework:^6.20.26 |
| 🐘Packagist | illuminate/database | ≥ 8.0.0&&< 8.40.0 | 8.40.0composer require illuminate/database:^8.40.0 |
| 🐘Packagist | illuminate/database | all versions | 6.20.26composer require illuminate/database:^6.20.26 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for laravel/framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update laravel/framework to 8.40.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4mg9-vhxq-vm7j is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4mg9-vhxq-vm7j can be triaged on real exposure rather than presence alone.
Tailored to GHSA-4mg9-vhxq-vm7j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-4mg9-vhxq-vm7j in your dependencies?
O3 Security finds GHSA-4mg9-vhxq-vm7j across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.