Is magento/magento1ee vulnerable?

Composer magento/magento1ee has 24 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

24advisories
0critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2019-7139SUPEE-11086 - RCE, XSS, CSRF and other vulnerabilitiesunknown0.0>=1.9.0.0 and <1.14.4.11.14.4.1
CVE-2019-7932PRODSECBUG-2351: Arbitrary code execution via crafted sitemap creationunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-8114PRODSECBUG-2462: Remote code execution via file upload in admin import featureunknown0.0>=1 and <1.14.4.31.14.4.3
CVE-2019-7911PRODSECBUG-2320: Arbitrary code execution due to unsafe handling of system configurationunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-7849PRODSECBUG-2095: Defense-in-depth session validation check implementedunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-7898PRODSECBUG-2300: Information about disabled products can be leaked due to inadequate validation checksunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-7899PRODSECBUG-2301: Names of disabled products can be leaked due to inadequate validation checksunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-8123PRODSECBUG-2445: Insufficient logging and monitoring of configuration changesunknown0.0>=1 and <1.14.4.31.14.4.3
CVE-2019-7889PRODSECBUG-2275: Unsafe functionality is exposed via email templates manipulationunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-8152PRODSECBUG-2344: Cross-Site Scripting via wysiwyg editorunknown0.0>=1 and <1.14.4.31.14.4.3
CVE-2019-7882PRODSECBUG-2246: Stored cross-site scripting in the WYSIWYG editorunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-7944PRODSECBUG-2378: Stored cross-site scripting in the Return Product comments featureunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-7945PRODSECBUG-2380: Stored cross-site scripting in the Currency Symbols fieldunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-7938Magento 2 Community Edition XSS Vulnerabilitymedium4.8>=1 and <1.14.4.21.14.4.2
CVE-2019-7875PRODSECBUG-2226: Stored cross-site scripting in the admin panelunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-7887PRODSECBUG-2270: Reflected cross-site scripting in the admin panelunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-7897PRODSECBUG-2299: Stored cross-site scripting in the admin panelunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-7909PRODSECBUG-2317: Stored cross-site scripting in admin panelunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-7934PRODSECBUG-2353: Stored cross-site scripting in the admin panelunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-7935PRODSECBUG-2363: Stored cross-site scripting in the admin panelunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-7940PRODSECBUG-2371: Stored cross-site scripting in the admin panelunknown0.0>=1 and <1.14.4.21.14.4.2
CVE-2019-7947PRODSECBUG-2387: Cross site request forgery attacks are possible via the gift card removal featureunknown0.0>=1 and <1.14.4.21.14.4.2
2017-02-07SUPEE-9652 - Remote Code Execution using mail vulnerabilityunknown0.0>=1.9.0.0 and <1.14.3.21.14.3.2
2018-11-28SUPEE-10975 - Security enhancements that help close RCE,XSS,CSRF and other vulnerabilitiesunknown0.0>=1.9.0.0 and <1.14.4.01.14.4.0

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.