CVE-2019-7876: Magento 2 Community Edition RCE Vulnerability

CVE-2019-7876 · Severity: low · CVSS 3 · Published 2022-05-24

Magento 2 Community Edition RCE Vulnerability

Technologies: magento/community-edition (Packagist), magento/product-community-edition (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2019-7876 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-7876 being exploited in the wild.
How severe is CVE-2019-7876?
Low severity, with a CVSS score of 3, published 24 May 2022.
Which products and versions are affected?
magento/community-edition (Packagist) ECOSYSTEM:introduced=2.1,fixed=2.1.18; magento/product-community-edition (Packagist) ECOSYSTEM:introduced=2.1,fixed=2.1.18.
Is there a fix for CVE-2019-7876?
Yes. magento/community-edition (Packagist): upgrade to 2.1.18 or later; magento/product-community-edition (Packagist): upgrade to 2.1.18 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-7876?
Check whether you run magento/community-edition (Packagist) or magento/product-community-edition (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

  • magento/community-edition (Packagist): upgrade to 2.1.18 or later
    composer require magento/community-edition:^2.1.18
  • magento/product-community-edition (Packagist): upgrade to 2.1.18 or later
    composer require magento/product-community-edition:^2.1.18

Affected products

  • magento/community-edition (Packagist) ECOSYSTEM:introduced=2.1,fixed=2.1.18
  • magento/product-community-edition (Packagist) ECOSYSTEM:introduced=2.1,fixed=2.1.18

Identifiers

  • CVE-2019-7876
  • GHSA-6qh6-v99h-vh4c

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.