CVERadar
HIGH · CVSS 4.0 8.7Public PoCEPSS 44.76% (p99)Threat level 61

CVE-2024-52301: CVE-2024-52301: Laravel is a web application framework. When the register_argc_argv php directive is set t…

laravel · framework · NVD published 2024-11-13 · posted 2024-11-14 · last modified 2026-06-17

What it is

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.

WeaknessCWE-88
CVSS vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (source: [email protected])
ATT&CK tacticsn/a

Exploitation evidence

First exploit evidence seen: 2024-11-14 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

3 public repositories from 3 accounts, first seen 2024-11-14. Most starred: Nyamort/CVE-2024-52301 (21 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

How to fix it

Fixed versions

  • laravel framework: upgrade to 6.20.45 or later
  • laravel framework: upgrade to 7.30.7 or later (affected from 7.0.0)
  • laravel framework: upgrade to 8.83.28 or later (affected from 8.0.0)
  • laravel framework: upgrade to 9.52.17 or later (affected from 9.0.0)
  • laravel framework: upgrade to 10.48.23 or later (affected from 10.0.0)
  • laravel framework: upgrade to 11.31.0 or later (affected from 11.0.0)

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources