facade/ignition
Packagist3 known CVEs affecting this package
Aggregated from OSV, GitHub Security Advisories, NVD, and vendor advisories. Each CVE links to its full detail page with vendor advisories, patches, fixed versions, and remediation guidance.
CVEs affecting facade/ignitionpage 1 of 1
- CVE-2020-13909CRITICALCVSS 9.8EG 9.8✓ Fixed in 1.16.152020-06-07
vulnerable: 1.0.0 ... 1.9.2 (67 versions)
The Ignition component before 2.0.5 for Laravel mishandles globals, _get, _post, _cookie, and _env. NOTE: in the 1.x series, versions 1.16.15 and later are unaffected as a consequence of the CVE-2021-43996 fix.
- CVE-2021-3129CRITICALCVSS 9.8EG 9.8⚠ KEV✓ Fixed in 1.6.152021-01-12
vulnerable: 1.0.0 ... 1.6.9 (41 versions)
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 de…
- CVE-2021-43996CRITICALCVSS 9.8EG 9.8✓ Fixed in 2.0.62021-11-17
vulnerable: 2.0.0, 2.0.1, 2.0.2, 2.0.4, 2.0.5
The Ignition component before 1.16.15, and 2.0.x before 2.0.6, for Laravel has a "fix variable names" feature that can lead to incorrect access control.
Check whether facade/ignition is used in your infrastructure
EchelonGraph scans your cloud and SBOMs to map every package to your actual deployments. See blast radius for facade/ignition CVEs against the assets you own.
Start Free Scan →