# CVE-2020-13909: Critical severity vulnerability in Ignition

Source: https://junglewise.ai/threats/cve-2020-13909-critical-severity-vulnerability-in-ignition  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2021-10-12  
License: CC BY 4.0 with a link back

CVE-2020-13909 · Severity: low · CVSS 3.1 · Published 2021-10-12

Critical severity vulnerability in Ignition

Technologies: [facade/ignition (Packagist)](https://junglewise.ai/threats/technologies/facade-ignition). Vendors: [Packagist](https://junglewise.ai/threats/vendors/packagist).

## Quick answers

**Is CVE-2020-13909 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2020-13909 being exploited in the wild.

**How severe is CVE-2020-13909?** Low severity, with a CVSS score of 3.1, published 12 October 2021.

**Which products and versions are affected?** facade/ignition (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=2.0.5.

**Is there a fix for CVE-2020-13909?** Yes. facade/ignition (Packagist): upgrade to 2.0.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2020-13909?** Check whether you run facade/ignition (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- facade/ignition (Packagist): upgrade to 2.0.5 or later

  ```sh
  composer require facade/ignition:^2.0.5
  ```


## Affected products

- facade/ignition (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=2.0.5

## Identifiers

- CVE-2020-13909
- GHSA-m5v7-pr32-mjx2

## Related threats

- [Incorrect Access Control in Ignition](https://junglewise.ai/threats/cve-2021-43996-incorrect-access-control-in-ignition)
- [Unauthenticated remote code execution in Ignition](https://junglewise.ai/threats/cve-2021-3129-laravel-ignition-file-upload-vulnerability)