How severe is GHSA-4mg9-vhxq-vm7j?

No CVSS score has been assigned to GHSA-4mg9-vhxq-vm7j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4mg9-vhxq-vm7j?

GHSA-4mg9-vhxq-vm7j affects the following packages: laravel/framework (Packagist), laravel/framework (Packagist), illuminate/database (Packagist), illuminate/database (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-4mg9-vhxq-vm7j?

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.

How do I detect GHSA-4mg9-vhxq-vm7j in my Packagist dependencies?

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.

How do I mitigate GHSA-4mg9-vhxq-vm7j if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is GHSA-4mg9-vhxq-vm7j actively exploited in the wild?

No public exploit code has been indexed for GHSA-4mg9-vhxq-vm7j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-4mg9-vhxq-vm7j published, and has it been updated?

GHSA-4mg9-vhxq-vm7j was published on April 29, 2021 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

SQL Server LIMIT / OFFSET SQL Injection in laravel/framework and illuminate/databaseGHSA-4mg9-vhxq-vm7j

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.

Published

Apr 29, 2021

Updated

Dec 2, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

4 pkgs affected

🐘laravel/framework🐘laravel/framework🐘illuminate/database🐘illuminate/database

Real-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

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`laravel/framework`	≥ 8.0.0&&< 8.40.0	8.40.0`composer require laravel/framework:^8.40.0`
🐘Packagist	`laravel/framework`	all versions	6.20.26`composer require laravel/framework:^6.20.26`
🐘Packagist	`illuminate/database`	≥ 8.0.0&&< 8.40.0	8.40.0`composer require illuminate/database:^8.40.0`
🐘Packagist	`illuminate/database`	all versions	6.20.26`composer require illuminate/database:^6.20.26`

Detection & mitigation playbook

Open-source dependency

Detect
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
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

### 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.

O3 Security · Impact-Aware SCA

Is GHSA-4mg9-vhxq-vm7j in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

SQL Server LIMIT / OFFSET SQL Injection in laravel/framework and illuminate/databaseGHSA-4mg9-vhxq-vm7j

Real-World Exposure

Description

Impact

Patches

Workarounds

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-4mg9-vhxq-vm7j in your dependencies?