CVE-2021-3129 — Laravel Ignition File Upload Vulnerability
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Used in ransomware campaigns (CISA)+10
- Public exploit/PoC (nuclei, metasploit, exploitdb, github)+20
- EPSS 99.9% (30-day exploitation probability)+15
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — github.com (NIST National Vulnerability Database)
- Composer Facade/ignition: fixed in version 2.5.2 — github.com (GitHub Security Advisories)
- Composer Facade/ignition: fixed in version 2.4.2 — github.com (GitHub Security Advisories)
- Composer Facade/ignition: fixed in version 1.16.14 — github.com (GitHub Security Advisories)
- Composer Facade/ignition: fixed in version 1.6.15 — github.com (GitHub Security Advisories)
CISA required action CISA
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
US federal deadline: Oct 9, 2023 — passed 1102 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Facade Ignition, Composer Facade/ignition).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Facade | Ignition | < 2.5.2 | Vulnerable | NIST National Vulnerability Database |
| Composer | Facade/ignition | ≥ 2.5.0 and < 2.5.2≥ 2.0.0 and < 2.4.2≥ 1.7.0 and < 1.16.14< 1.6.15 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 9.8 | CVSS 3.1 | Critical | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
| 7.5 | CVSS 2.0 | High | 10.0 | 6.4 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- Unauthenticated remote code execution in Ignition excellent Jan 13, 2021
- Laravel 8.4.2 debug mode - Remote code execution Jan 14, 2021
- Exploit for CVE-2021-3129 ★ 289 Jan 13, 2021
- Laravel <= v8.4.2 debug mode: Remote code execution (CVE-2021-3129) ★ 166 Feb 18, 2021
- Laravel RCE Exploit PoC - CVE-2021-3129 (user-friendly with automatic log path detection) ★ 158 Apr 16, 2022
- Laravel debug rce ★ 134 Jan 22, 2021
- SecPros-Team/laravel-CVE-2021-3129-EXP ★ 79 Jan 25, 2021
- Exploit for CVE-2021-3129 ★ 69 Jan 27, 2021
- crisprss/Laravel_CVE-2021-3129_EXP ★ 18 Jan 27, 2021
- Laravel Debug mode RCE漏洞（CVE-2021-3129）poc / exp ★ 13 Mar 4, 2023
- PoC for CVE-2021-3129 (Laravel) ★ 12 Oct 1, 2021
- CVE-2021-3129 (Laravel Ignition RCE Exploit) ★ 10 Sep 29, 2024
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 99.94%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Hunt retroactively in logs from before Sep 18, 2023 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · composer/facade/ignition
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · facade/ignition
- CVSS changed · 9.8
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- 2023
- Added to CISA KEV catalog
- 2021
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
9 on the record
- github.com/facade/ignition/pull/334
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- www.ambionics.io/blog/laravel-debug-rce
- github.com/advisories/GHSA-4qwp-7c67-jmcc
- github.com/facade/ignition/commit/11ffca14abd22db779d90b12e193f8000f6d184b
- github.com/FriendsOfPHP/security-advisories/blob/master/facade/ignition/CVE-2021
- nvd.nist.gov/vuln/detail/CVE-2021-3129
- packetstormsecurity.com/files/165999/Ignition-Remote-Code-Execution.html
- packetstormsecurity.com/files/162094/Ignition-2.5.1-Remote-Code-Execution.html
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2021-3129 is "Laravel Ignition File Upload Vulnerability", rated Critical. It affects Ignition (Facade); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.8 describes technical severity. EPSS 99.94% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.