CVE-2020-13909 json
Critical severity vulnerability in Ignition
published 6y ago modified 4mo ago also GHSA-m5v7-pr32-mjx2 , EUVD-2021-2223
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist facade/ignition 1.16.15, 2.0.5
- facade ignition 1.16.15, 2.0.5
Is CVE-2020-13909 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.52% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | facade/ignition | >=2.0.0, <2.0.5 <1.16.15 |
2.0.5 1.16.15 |
References
-
github.com
/facade/ignition/compare/2.0.4...2.0.5
web, patch, third-party-advisory
-
github.com
/facade/ignition/releases/tag/2.0.5
web, release-notes, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-13909
advisory
-
github.com
/github/advisory-database/issues/2316
web
-
github.com
/facade/ignition
package
-
cve.org
/CVERecord?id=CVE-2020-13909
web
Sources
- CVE List CVE-2020-13909
- GitHub Advisory GHSA-m5v7-pr32-mjx2
- NVD CVE-2020-13909
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.