How severe is CVE-2020-13909?

CVE-2020-13909 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-13909?

CVE-2020-13909 affects the following packages: facade/ignition (Packagist), facade/ignition (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2020-13909?

Update facade/ignition to 2.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-13909 is resolved across your whole dependency graph.

How do I detect CVE-2020-13909 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for facade/ignition, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2020-13909 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2020-13909 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-13909 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2020-13909?

CVE-2020-13909 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 73th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2020-13909 published, and has it been updated?

CVE-2020-13909 was published on June 7, 2020 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

CVE-2020-13909 — ignition

CRITICAL

CVE-2020-13909 is a critical-severity (CVSS 9.8) vulnerability in facade/ignition. A fix is available for facade/ignition — see the affected versions and patch details below.

Critical severity vulnerability in Ignition

Also known asGHSA-m5v7-pr32-mjx2

Published

Jun 7, 2020

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2020-13909 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

🐘facade/ignition🐘facade/ignition

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

The Ignition page before version 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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`facade/ignition`	≥ 2.0.0&&< 2.0.5	2.0.5`composer require facade/ignition:^2.0.5`
🐘Packagist	`facade/ignition`	all versions	1.16.15`composer require facade/ignition:^1.16.15`

Affected Products

1 product · 2 configurations

Application

ignitionfacade

≥ 2.0.0 && < 2.0.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for facade/ignition, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update facade/ignition to 2.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-13909 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

The Ignition page before version 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.

O3 Security · Impact-Aware SCA

Is CVE-2020-13909 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works