dbcve.org
FrameworkFramework / library · Laravel

CVE-2024-52301

HIGH · 7.5 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 6.20.45 / 7.30.7 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Laravel is a web application framework. 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. The vulnerability fixed in 6.20.45, 7.30.7, 8.83.28, 9.52.17, 10.48.23, and 11.31.0. The framework now ignores argv values for environment detection on non-cli SAPIs.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Laravel frameworks 6.x through 11.x contain an environment detection vulnerability when the PHP directive `register_argc_argv` is enabled. Attackers can manipulate the request environment by sending specially crafted query strings (argv values), potentially altering framework behavior. The fix makes the framework ignore argv values for environment detection on non-CLI Server APIs.

MitigationDisable the `register_argc_argv` PHP directive in php.ini or upgrade to the patched Laravel versions (6.20.45, 7.30.7, 8.83.28, 9.52.17, 10.48.23, or 11.31.0).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FrameworkFramework / library
Affected:< 6.20.45>= 7.0.0, < 7.30.7>= 8.0.0, < 8.83.28>= 9.0.0, < 9.52.17>= 10.0.0, < 10.48.23>= 11.0.0, < 11.31.0
Debian LinuxOperating system
Affected:= 11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Laravel version
    Locate the Laravel version file (typically vendor/laravel/framework/src/Illuminate/Foundation/Application.php or check composer.json) and note the version number
    Affected if The installed version falls within any of these ranges: < 6.20.45; >= 7.0.0 and < 7.30.7; >= 8.0.0 and < 8.83.28; >= 9.0.0 and < 9.52.17; >= 10.0.0 and < 10.48.23; >= 11.0.0 and < 11.31.0
  2. Verify PHP register_argc_argv directive status
    Run `php -i` or `php -r 'echo ini_get("register_argc_argv");'` to check the current value of the register_argc_argv directive
    Affected if The directive returns "1", "On", or "true" (enabled)
  3. Confirm Server API type
    Check the Server API by running `php -i | grep "Server API"` or `php_sapi_name()` in a PHP script
    Affected if The Server API is NOT CLI (for example, it shows FPM/FastCGI, Apache, or other web server SAPI) - the vulnerability affects non-CLI Server APIs

You are affected if your Laravel version is vulnerable (within the listed ranges) AND register_argc_argv is enabled AND you are running on a non-CLI Server API (web server).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.20.45 / 7.30.7 / 8.83.28 or later
Fixed in 6.20.457.30.78.83.28
Interim mitigation

Disable the `register_argc_argv` PHP directive in php.ini or upgrade to the patched Laravel versions (6.20.45, 7.30.7, 8.83.28, 9.52.17, 10.48.23, or 11.31.0).

Recommended fix High confidence

Laravel Framework 6.20.45, 7.30.7, 8.83.28, 9.52.17, 10.48.23, or 11.31.0 depending on current major version

  1. 1. Identify the current Laravel Framework version by checking the composer.json file or running `php artisan --version`
  2. 2. Determine the appropriate upgrade target based on your current major version: for 6.x upgrade to 6.20.45, for 7.x upgrade to 7.30.7, for 8.x upgrade to 8.83.28, for 9.x upgrade to 9.52.17, for 10.x upgrade to 10.48.23, or for 11.x upgrade to 11.31.0
  3. 3. Update the composer.json require section to specify the target version: `composer require laravel/framework:^X.XX --no-update` (replace X.XX with your major.minor version)
  4. 4. Run `composer update laravel/framework` to install the patched version
  5. 5. Run `php artisan --version` to confirm the upgrade was successful
  6. 6. Test application functionality to ensure no regressions
Caveat Upgrading across major versions may introduce breaking changes; review Laravel upgrade guides for your specific version jump

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Framework Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52301 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-52301 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data