facade/ignition vulnerabilities
A beautiful error page for Laravel applications.
- Registry
- Composer
- Latest
- 2.17.7
- License
- MIT
3 known advisories
The latest version, 2.17.7, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
composer require facade/ignition:^2.17.7Is your project on an affected facade/ignition?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for facade/ignition
Incorrect Access Control in Ignition
- Affected
- <1.16.15 · >=2.0.0 <2.0.6
- Fixed in
- 1.16.15, 2.0.6
Critical severity vulnerability in Ignition
- Affected
- >=2.0.0 <2.0.5 · <1.16.15
- Fixed in
- 1.16.15, 2.0.5
Unauthenticated remote code execution in Ignition
- Affected
- >=2.5.0 <2.5.2 · >=2.0.0 <2.4.2 · >=1.7.0 <1.16.14 · <1.6.15
- Fixed in
- 1.6.15, 1.16.14, 2.4.2, 2.5.2
Is your facade/ignition version vulnerable?
- facade/ignition 2.17No known advisories in 2.17.7
- facade/ignition 2.16No known advisories in 2.16.1
- facade/ignition 2.15No known advisories in 2.15.0
- facade/ignition 2.14No known advisories in 2.14.1
- facade/ignition 2.13No known advisories in 2.13.1
- facade/ignition 2.12No known advisories in 2.12.1
- facade/ignition 1.18No known advisories in 1.18.1
- facade/ignition 1.17No known advisories in 1.17.0
- facade/ignition 1.16No known advisories in 1.16.15
- facade/ignition 1.153 advisories in 1.15.0
- facade/ignition 1.143 advisories in 1.14.0
- facade/ignition 1.133 advisories in 1.13.1
Which of your client projects still run an old facade/ignition?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.