Summary
laravel framework SQL Injection via limit and offset functions
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.
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.
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This problem has been patched on Laravel versions 6.20.26, 7.30.5, and 8.40.0.
Frequently Asked Questions
- What is GHSA-WQ8P-MQVG-2P5H? GHSA-WQ8P-MQVG-2P5H is a high-severity SQL injection vulnerability in laravel/framework (composer), affecting versions >= 6.0.0, < 6.20.26. It is fixed in 6.20.26, 7.30.5, 8.40.0. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- Which versions of laravel/framework are affected by GHSA-WQ8P-MQVG-2P5H? laravel/framework (composer) versions >= 6.0.0, < 6.20.26 is affected.
- Is there a fix for GHSA-WQ8P-MQVG-2P5H? Yes. GHSA-WQ8P-MQVG-2P5H is fixed in 6.20.26, 7.30.5, 8.40.0. Upgrade to this version or later.
- Is GHSA-WQ8P-MQVG-2P5H exploitable, and should I be worried? Whether GHSA-WQ8P-MQVG-2P5H is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-WQ8P-MQVG-2P5H is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-WQ8P-MQVG-2P5H?
- Upgrade
laravel/frameworkto 6.20.26 or later - Upgrade
laravel/frameworkto 7.30.5 or later - Upgrade
laravel/frameworkto 8.40.0 or later
- Upgrade