+44 1865 950 828 Secure Your Business
Actively exploitedKnown ransomware use

CVE-2021-3129 Laravel Ignition File Upload Vulnerability

Laravel Ignition contains a file upload vulnerability that allows unauthenticated remote attackers to execute malicious code due to insecure usage of file_get_contents() and file_put_contents().

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch nowCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 18 Sep 2023.
  • CISA lists it as known to be used in ransomware campaigns.
  • Rated Critical severity (CVSS 9.8, scored by CISA).
  • It has been in the catalogue for 1,145 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

Ignition before 2.5.2, as used in Laravel and other products, allows unauthenticated remote attackers to execute arbitrary code because of insecure usage of file_get_contents() and file_put_contents(). This is exploitable on sites using debug mode with Laravel before 8.4.2.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Laravel Ignition. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Vendor Advisories

Regulation

The Compliance Clock

Cyber EssentialsRated critical, so if it affects devices in your Cyber Essentials scope, the update must be installed within 14 days of the vendor releasing it.NIS2If exploitation causes a significant incident, essential and important entities owe their CSIRT an early warning within 24 hours and a notification within 72 hours.DORAFinancial entities must classify ICT incidents and send an initial notification for a major incident within strict deadlines, with exploited flaws a common cause.US federal (BOD 22-01)Federal civilian agencies had until 9 Oct 2023 to remediate. A sensible benchmark for everyone else.

General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.

Stay Ahead

More Exploited Laravel Flaws

Get alerts for LaravelWe email you when a new Laravel vulnerability is confirmed as exploited. Add more vendors on Threat Watch.

By signing up you agree to receive Threat Watch alerts. Unsubscribe at any time. See our Privacy Policy.

CVE-2025-54068Laravel Livewire Code Injection VulnerabilityAdded 20 Mar 2026CVE-2018-15133Laravel Deserialization of Untrusted Data VulnerabilityAdded 16 Jan 2024

All 3 exploited Laravel vulnerabilities

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2021-3129 and every other exploited flaw on the list.

Check My Exposure
Evidence

Sources

  1. CISA Known Exploited Vulnerabilities catalogue
  2. NVD: CVE-2021-3129
  3. CVE record: CVE-2021-3129
  4. FIRST EPSS
  5. github.com/facade/ignition/releases/tag/2.5.2
  6. ambionics.io/blog/laravel-debug-rce
  7. github.com/facade/ignition/pull/334
  8. packetstormsecurity.com/files/162094/Ignition-2.5.1-Remote-Code-Execution.html
  9. packetstormsecurity.com/files/165999/Ignition-Remote-Code-Execution.html