What is CVE-2024-52301?

CVE-2024-52301 is a high-severity security vulnerability in laravel/framework (composer), affecting versions < 6.20.45. It is fixed in 6.20.45, 7.30.7, 8.83.28, 9.52.17, 10.48.23, 11.31.0.

Which versions of laravel/framework are affected by CVE-2024-52301?

laravel/framework (composer) versions < 6.20.45 is affected.

Is there a fix for CVE-2024-52301?

Yes. CVE-2024-52301 is fixed in 6.20.45, 7.30.7, 8.83.28, 9.52.17, 10.48.23, 11.31.0. Upgrade to this version or later.

Is CVE-2024-52301 exploitable, and should I be worried?

Whether CVE-2024-52301 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.

What actually determines whether CVE-2024-52301 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.

CVE-2024-52301 in laravel/framework | Intelligent Application Security

Q: Which versions of laravel/framework are affected by CVE-2024-52301?

laravel/framework (composer) versions < 6.20.45 is affected.

Q: Is there a fix for CVE-2024-52301?

Yes. CVE-2024-52301 is fixed in 6.20.45, 7.30.7, 8.83.28, 9.52.17, 10.48.23, 11.31.0. Upgrade to this version or later.

Q: Is CVE-2024-52301 exploitable, and should I be worried?

Whether CVE-2024-52301 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.

Q: What actually determines whether CVE-2024-52301 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.

Q: How do I fix CVE-2024-52301?

Upgrade: laravel/framework to 6.20.45 or later, laravel/framework to 7.30.7 or later, laravel/framework to 8.83.28 or later, laravel/framework to 9.52.17 or later, laravel/framework to 10.48.23 or later, laravel/framework to 11.31.0 or later.

Summary

Description

When the register_argc_argv php directive is set to on , and users call any URL with a special crafted query string, they are able to change the environment used by the framework when handling the request.

Resolution

The framework now ignores argv values for environment detection on non-cli SAPIs.

Impact

Affected versions

laravel/framework (< 6.20.45) laravel/framework (>= 7.0.0, < 7.30.7) laravel/framework (>= 8.0.0, < 8.83.28) laravel/framework (>= 9.0.0, < 9.52.17) laravel/framework (>= 10.0.0, < 10.48.23) laravel/framework (>= 11.0.0, < 11.31.0)

Security releases

laravel/framework → 6.20.45 (composer) laravel/framework → 7.30.7 (composer) laravel/framework → 8.83.28 (composer) laravel/framework → 9.52.17 (composer) laravel/framework → 10.48.23 (composer) laravel/framework → 11.31.0 (composer)

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.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

laravel/framework to 6.20.45 or later; laravel/framework to 7.30.7 or later; laravel/framework to 8.83.28 or later; laravel/framework to 9.52.17 or later; laravel/framework to 10.48.23 or later; laravel/framework to 11.31.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-52301? CVE-2024-52301 is a high-severity security vulnerability in laravel/framework (composer), affecting versions < 6.20.45. It is fixed in 6.20.45, 7.30.7, 8.83.28, 9.52.17, 10.48.23, 11.31.0.
Which versions of laravel/framework are affected by CVE-2024-52301? laravel/framework (composer) versions < 6.20.45 is affected.
Is there a fix for CVE-2024-52301? Yes. CVE-2024-52301 is fixed in 6.20.45, 7.30.7, 8.83.28, 9.52.17, 10.48.23, 11.31.0. Upgrade to this version or later.
Is CVE-2024-52301 exploitable, and should I be worried? Whether CVE-2024-52301 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 CVE-2024-52301 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 CVE-2024-52301?
- Upgrade laravel/framework to 6.20.45 or later
- Upgrade laravel/framework to 7.30.7 or later
- Upgrade laravel/framework to 8.83.28 or later
- Upgrade laravel/framework to 9.52.17 or later
- Upgrade laravel/framework to 10.48.23 or later
- Upgrade laravel/framework to 11.31.0 or later

Other vulnerabilities in laravel/framework

CVE-IDSeverityPackage summary

GHSA-CRMM-HGP2-WGRPMediumlaravel/framework: Laravel Framework: Temporary Signed URL Path Confusion GHSA-5VG9-5847-VVMQHighlaravel/framework: Laravel Framework: CRLF injection in default email rule CVE-2024-13918Mediumlaravel/framework: Laravel framework susceptible to reflected cross-site scripting CVE-2024-13919Mediumlaravel/framework: Laravel framework susceptible to reflected cross-site scripting CVE-2025-27515Mediumlaravel/framework: Laravel has a File Validation Bypass

Summary

Description

Resolution

Impact

Affected versions

Security releases

Kodem intelligence

Remediation advice

Frequently Asked Questions

Other vulnerabilities in laravel/framework

Other vulnerabilities in laravel/framework

Stop the waste.Protect your environment with Kodem.

Stop the waste.
Protect your environment with Kodem.