CVE-2019-7912: Magento Filter extension bypass via crafted store configuration keys

Published Jun 25, 2019
·
Updated

A file upload filter bypass exists in Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, Magento 2.3 prior to 2.3.2. This can be exploited by an authenticated user with admin privileges to edit configuration keys to remove file extension filters, potentially resulting in the malicious upload and execution of malicious files on the server.

Other sources

Magento Filter extension bypass via crafted store configuration keys

— Packagist

PRODSECBUG-2321: Filter extension bypass via crafted store configuration keys

Affected Software

13 affected componentsFixes available
composer/magento/product-community-edition>=2.1, <2.1.18, >=2.2, <2.2.9, >=2.3, <2.3.2
composer/magento/community-edition>=2.3<2.3.2
2.3.2
composer/magento/community-edition>=2.2<2.2.9
2.2.9
composer/magento/community-edition>=2.1<2.1.18
2.1.18
Magento Magento>=2.1.0<2.1.18
Magento Magento>=2.2.0<2.2.9
Magento Magento>=2.3.0<2.3.2
composer/magento/community-edition>=2.3, <2.3.2
2.3.2
composer/magento/community-edition>=2.2, <2.2.9
2.2.9
composer/magento/community-edition>=2.1, <2.1.18
2.1.18
composer/magento/product-community-edition>=2.1, <2.1.18
2.1.18
composer/magento/product-community-edition>=2.2, <2.2.9
2.2.9
composer/magento/product-community-edition>=2.3, <2.3.2
2.3.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/magento/community-edition to a version that resolves this vulnerability.

    Fixed in 2.3.2
  2. Upgrade

    Upgrade composer/magento/community-edition to a version that resolves this vulnerability.

    Fixed in 2.2.9
  3. Upgrade

    Upgrade composer/magento/community-edition to a version that resolves this vulnerability.

    Fixed in 2.1.18
  4. Upgrade

    Upgrade composer/magento/product-community-edition to a version that resolves this vulnerability.

    Fixed in 2.1.18
  5. Upgrade

    Upgrade composer/magento/product-community-edition to a version that resolves this vulnerability.

    Fixed in 2.2.9
  6. Upgrade

    Upgrade composer/magento/product-community-edition to a version that resolves this vulnerability.

    Fixed in 2.3.2
  7. Upgrade

    Upgrade Magento to a version that resolves this vulnerability.

    Fixed in 2.1.18
  8. Upgrade

    Upgrade Magento to a version that resolves this vulnerability.

    Fixed in 2.2.9
  9. Upgrade

    Upgrade Magento to a version that resolves this vulnerability.

    Fixed in 2.3.2

Event History

Jun 25, 2019
Advisory Published
12:00 AM
Data Sourced
via Packagist·12:00 AM
DescriptionSeverityAffected Software
Aug 2, 2019
CVE Published
via MITRE·09:27 PM
Data Sourced
via MITRE·09:27 PM
DescriptionWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeaknessAffected Software
May 24, 2022
Advisory Published
via GitHub·04:52 PM
Data Sourced
via GitHub·04:52 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2019-7912?

CVE-2019-7912 is classified as a high severity vulnerability due to the potential for authenticated users with admin privileges to upload malicious files.

2

How do I fix CVE-2019-7912?

To fix CVE-2019-7912, update Magento to version 2.1.18, 2.2.9, or 2.3.2 or later.

3

Who is affected by CVE-2019-7912?

CVE-2019-7912 affects Magento versions 2.1 prior to 2.1.18, 2.2 prior to 2.2.9, and 2.3 prior to 2.3.2.

4

What can an attacker do with CVE-2019-7912?

An attacker with admin privileges can exploit CVE-2019-7912 to bypass file upload filters and potentially upload malicious files.

5

Is there a workaround for CVE-2019-7912?

There is no official workaround for CVE-2019-7912; patching to a secure version is the recommended action.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203