CVE-2024-52301

HIGHNVD 7.57.7▲
EchelonGraph scoreHIGH confidence

Score elevated to 7.7 because EPSS predicts 38% probability of exploitation within the next 30 days (top 1.6% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 38%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.7(high)
EG Risk
66(Track)
EG Risk 66/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity77% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
98.4%
KEV
Not listed

Published

November 12, 2024

Last Modified

August 26, 2025

References (2)

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
laravel/frameworkv11.0.0 ... v11.9.2 (54 versions)11.31.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 02:43 UTCEG score recompute▲ 0.20
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-21 15:23 UTCEPSS rescore
  5. 2026-07-20 17:06 UTCEPSS rescore
  6. 2026-07-19 02:28 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:03 UTCEPSS rescore
  9. 2026-07-18 10:03 UTCEPSS rescore
  10. 2026-07-16 17:02 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 16:56 UTCEPSS rescore
  13. 2026-07-15 01:59 UTCEPSS rescore
  14. 2026-07-15 01:59 UTCEPSS rescore
  15. 2026-07-13 22:29 UTCEPSS rescore
  16. 2026-07-13 20:08 UTCOSV refresh
  17. 2026-07-13 06:12 UTCEPSS rescore
  18. 2026-07-12 05:45 UTCEPSS rescore
  19. 2026-07-12 05:45 UTCEPSS rescore
  20. 2026-07-11 08:26 UTCEPSS rescore
  21. 2026-07-09 19:09 UTCEPSS rescore
  22. 2026-07-09 19:09 UTCEPSS rescore
  23. 2026-07-08 15:14 UTCEPSS rescore
  24. 2026-07-07 13:45 UTCEPSS rescore
  25. 2026-07-05 02:29 UTCEPSS rescore
Show 56 more
  1. 2026-07-01 15:05 UTCEPSS rescore
  2. 2026-06-29 14:05 UTCEPSS rescore
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 04:55 UTCEPSS rescore
  5. 2026-06-28 04:55 UTCEPSS rescore
  6. 2026-06-27 03:07 UTCEPSS rescore
  7. 2026-06-27 03:07 UTCEPSS rescore
  8. 2026-06-25 17:46 UTCOSV refresh
  9. 2026-06-25 13:49 UTCEPSS rescore
  10. 2026-06-24 14:04 UTCEPSS rescore
  11. 2026-06-24 14:04 UTCEPSS rescore
  12. 2026-06-23 21:32 UTCEPSS rescore
  13. 2026-06-23 21:32 UTCEPSS rescore
  14. 2026-06-22 14:25 UTCEPSS rescore
  15. 2026-06-22 14:25 UTCEPSS rescore
  16. 2026-06-21 01:59 UTCEPSS rescore
  17. 2026-06-21 01:58 UTCEPSS rescore
  18. 2026-06-18 17:52 UTCEPSS rescore
  19. 2026-06-18 17:52 UTCEPSS rescore
  20. 2026-06-17 17:52 UTCEPSS rescore
  21. 2026-06-17 17:52 UTCEPSS rescore
  22. 2026-06-16 17:52 UTCEPSS rescore
  23. 2026-06-16 17:52 UTCEPSS rescore
  24. 2026-06-15 17:47 UTCEPSS rescore
  25. 2026-06-12 23:11 UTCEPSS rescore
  26. 2026-06-12 23:11 UTCEPSS rescore
  27. 2026-06-11 13:59 UTCEPSS rescore
  28. 2026-06-10 22:18 UTCEPSS rescore
  29. 2026-06-08 07:28 UTCOSV refresh
  30. 2026-06-07 15:24 UTCEPSS rescore
  31. 2026-06-07 15:24 UTCEPSS rescore
  32. 2026-06-06 13:46 UTCEPSS rescore
  33. 2026-06-06 13:46 UTCEPSS rescore
  34. 2026-06-05 22:46 UTCEPSS rescore
  35. 2026-06-05 22:46 UTCEPSS rescore
  36. 2026-06-05 06:09 UTCEPSS rescore
  37. 2026-06-05 06:09 UTCEPSS rescore
  38. 2026-06-04 13:11 UTCEPSS rescore
  39. 2026-06-04 13:11 UTCEPSS rescore
  40. 2026-06-02 20:12 UTCEPSS rescore
  41. 2026-06-01 13:51 UTCEPSS rescore
  42. 2026-06-01 13:51 UTCEPSS rescore
  43. 2026-05-31 00:16 UTCEPSS rescore
  44. 2026-05-31 00:16 UTCEPSS rescore
  45. 2026-05-29 13:43 UTCEPSS rescore
  46. 2026-05-28 13:44 UTCEPSS rescore
  47. 2026-05-28 13:44 UTCEPSS rescore
  48. 2026-05-28 13:44 UTCEPSS rescore
  49. 2026-05-27 13:40 UTCEPSS rescore
  50. 2026-05-27 13:40 UTCEPSS rescore
  51. 2026-05-26 13:43 UTCEPSS rescore
  52. 2026-05-26 13:43 UTCEPSS rescore
  53. 2026-05-26 07:18 UTCEPSS rescore
  54. 2026-05-26 07:18 UTCEPSS rescore
  55. 2026-05-26 07:18 UTCEPSS rescore
  56. 2026-05-23 18:24 UTCEG score recompute

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCmartinhaunschmid/CVE-2024-52301-Research
    First seen Nov 15, 2024

    A bit of research around CVE-2024-52301

    Open source ↗
  • GitHub PoCNyamort/CVE-2024-52301
    First seen Nov 14, 2024
    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-52301?
CVE-2024-52301 is a high vulnerability published on November 12, 2024. Laravel is a web application framework. When the registerargcargv 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,…
When was CVE-2024-52301 disclosed?
CVE-2024-52301 was first published in the National Vulnerability Database on November 12, 2024, with the most recent update on August 26, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-52301 actively exploited?
CVE-2024-52301 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-52301?
CVE-2024-52301 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.7.
How do I remediate CVE-2024-52301?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-52301, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-52301

Explore →

Is Your Infrastructure Affected by CVE-2024-52301?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs