VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

magento/community-edition: vulnerability history, versions and safety

magento/community-edition is a package in the Packagist ecosystem. Vulert records 305 vulnerabilities for it across 120 releases, from Nov 2019 to Oct 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
305 vulnerabilities recorded C39 H83 M168 L15
i
42 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all magento/community-edition vulnerabilities

Vulert verdict on magento/community-edition i

Updated on 23 Oct 2026

Careful: 42 of the 305 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 305 vulnerabilities on record across 5 years, none in the last year.

What to do: Plan around the 42 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 305 over 5 years · 0 in the last year i
  • Latest disclosure 14 Oct 2025 i
  • Highest CVSS 10.0 i
  • With no published fix 42 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for magento/community-edition, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2.4.9-alpha2 H1 M1 Yes Details →
2.4.9-alpha1 H1 M1 Yes Details →
2.4.8 C1 Yes Details →
2.4.8-beta2 C1 Yes Details →
2.4.8-beta1 C2 Yes Details →
2.4.7-p3 H11 M9 L3 Yes Details →
2.4.7-p2 H13 M26 L4 Yes Details →
2.4.7-p1 H13 M31 L4 Yes Details →
2.4.7 C1 H14 M30 L4 No Details →
2.4.7-beta3 H13 M26 L4 Yes Details →
2.4.7-beta2 H13 M26 L4 Yes Details →
2.4.7-beta1 H13 M34 L5 Yes Details →
2.4.6 H5 M11 L5 No Details →
2.4.5-p14 C1 No Details →
2.4.5-p13 C1 No Details →
2.4.5-p12 C1 No Details →
2.4.5-p11 C1 No Details →
2.4.5-p10 C1 No Details →
2.4.5-p9 C1 No Details →
2.4.5-p8 C1 No Details →
2.4.5-p7 C1 No Details →
2.4.5-p6 C1 No Details →
2.4.5-p5 C1 No Details →
2.4.5-p4 C1 No Details →
2.4.5-p3 C1 No Details →
2.4.5-p2 C1 No Details →
2.4.5-p1 C1 H1 No Details →
2.4.5 C1 No Details →
2.4.4-p13 C1 H1 No Details →
2.4.4-p12 C1 H1 M1 No Details →
2.4.4-p11 C1 H1 M1 No Details →
2.4.4-p10 C1 H1 M1 No Details →
2.4.4-p9 C1 H1 M1 No Details →
2.4.4-p8 C1 H1 M1 No Details →
2.4.4-p7 C1 H1 M1 No Details →
2.4.4-p6 C1 H1 M1 No Details →
2.4.4-p5 C1 H1 M1 No Details →
2.4.4-p4 C1 H1 M1 No Details →
2.4.4-p3 C1 H1 M1 No Details →
2.4.4-p2 C1 H1 M3 No Details →
2.4.4-p1 C1 H2 M4 No Details →
2.4.4 C2 H1 M1 L1 No Details →
2.4.3-p3 C1 H1 M1 No Details →
2.4.3-p2 C1 H1 M2 No Details →
2.4.3-p1 C1 H1 M2 No Details →
2.4.3 C1 H1 M2 No Details →
2.4.2-p2 C1 H1 M2 No Details →
2.4.2-p1 C1 H1 M2 No Details →
2.4.2 C1 H2 M6 L1 No Details →
2.4.1-p1 C1 H2 M6 L1 No Details →
2.4.1 C1 H2 M8 L1 No Details →
2.4.0-p1 C2 H2 M10 L1 No Details →
2.4.0 C2 H2 M10 L1 No Details →
2.3.7-p4 C2 H1 M3 No Details →
2.3.7-p3 C3 H5 M6 No Details →
2.3.7-p2 C4 H5 M6 No Details →
2.3.7-p1 C4 H5 M6 No Details →
2.3.7 C4 H5 M6 No Details →
2.3.6-p1 C4 H5 M6 No Details →
2.3.6 C9 H6 M10 No Details →
2.3.5-p2 C10 H8 M14 L3 No Details →
2.3.5-p1 C11 H8 M17 L3 No Details →
2.3.5 C11 H8 M17 L3 No Details →
2.3.4-p2 C11 H8 M17 L3 No Details →
2.3.4 C14 H10 M19 L3 No Details →
2.3.3-p1 C15 H11 M21 L3 No Details →
2.3.3 C14 H11 M21 L3 No Details →
2.3.2-p2 C14 H11 M21 L3 No Details →
2.3.2 C15 H11 M22 L3 No Details →
2.3.1 C15 H11 M23 L3 No Details →
2.3.0 C15 H11 M23 L3 No Details →
2.2.11 C17 H7 M16 L3 No Details →
2.2.10 C18 H7 M17 L3 No Details →
2.2.9 C22 H22 M43 L3 No Details →
2.2.8 C22 H22 M44 L3 No Details →
2.2.7 C22 H22 M44 L3 No Details →
2.2.6 C22 H22 M44 L3 No Details →
2.2.5 C22 H23 M44 L3 No Details →
2.2.4 C22 H23 M44 L3 No Details →
2.2.3 C22 H23 M44 L3 No Details →
2.2.2 C22 H23 M44 L3 No Details →
2.2.1 C22 H23 M44 L3 No Details →
2.2.0 C22 H23 M44 L3 No Details →
2.1.18 C17 H11 M20 L3 No Details →
2.1.17 C18 H38 M61 L3 No Details →
2.1.16 C18 H38 M61 L3 No Details →
2.1.15 C19 H38 M61 L3 No Details →
2.1.14 C19 H38 M62 L3 No Details →
2.1.13 C20 H38 M62 L3 No Details →
2.1.12 C20 H38 M62 L3 No Details →
2.1.11 C20 H38 M62 L3 No Details →
2.1.10 C20 H38 M62 L3 No Details →
2.1.9 C20 H38 M62 L3 No Details →
2.1.8 C20 H38 M62 L3 No Details →
2.1.7 C20 H38 M62 L3 No Details →
2.1.6 C20 H38 M62 L3 No Details →
2.1.5 C20 H38 M62 L3 No Details →
2.1.4 C20 H38 M62 L3 No Details →
2.1.3 C20 H38 M62 L3 No Details →
2.1.2 C20 H38 M62 L3 No Details →
2.1.1 C20 H38 M62 L3 No Details →
2.1.0 C20 H38 M62 L3 No Details →
2.1.0-rc3 C19 H18 M28 L3 No Details →
2.1.0-rc2 C19 H18 M28 L3 No Details →
2.1.0-rc1 C19 H18 M28 L3 No Details →
2.0.18 C17 H8 M16 L3 No Details →
2.0.17 C17 H8 M16 L3 No Details →
2.0.16 C17 H8 M16 L3 No Details →
2.0.15 C17 H8 M16 L3 No Details →
2.0.14 C17 H8 M16 L3 No Details →
2.0.13 C17 H8 M16 L3 No Details →
2.0.12 C17 H8 M16 L3 No Details →
2.0.11 C17 H8 M16 L3 No Details →
2.0.10 C17 H8 M16 L3 No Details →
2.0.9 C17 H8 M17 L3 No Details →
2.0.8 C17 H8 M17 L3 No Details →
2.0.7 C17 H8 M17 L3 No Details →
2.0.6 C17 H8 M17 L3 No Details →
2.0.5 C17 H8 M17 L3 No Details →
2.0.4 C17 H8 M17 L3 No Details →

Newest 120 of 179 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 7
  • 2022 194
  • 2023 29
  • 2024 45
  • 2025 30

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 305 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for magento/community-edition

The 5 most severe of 305 vulnerabilities recorded for this package

Search all 305 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-35698: Magento Community Edition Stored XSS Vulnerability 10.0 high No fix published 15 Oct 2022
Magento Broken authentication and session management 9.8 critical 2.2.10 24 May 2022
CVE-2019-8158: Magento 2 Community Edition XML Injection 9.8 critical 2.2.10 24 May 2022
CVE-2020-3716: Magento Deserialization Vulnerability 9.8 critical 2.2.11 24 May 2022
CVE-2019-7139: Magento 2 Community Edition SQLi Vulnerability 9.8 critical 2.1.18 24 May 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About magento/community-edition

Is magento/community-edition safe to use?

Vulert records 305 vulnerabilities for magento/community-edition in Packagist: 39 critical, 83 high, 168 medium and 15 low. 42 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does magento/community-edition have?

305 vulnerabilities are recorded for magento/community-edition in the Packagist ecosystem: 39 critical, 83 high, 168 medium and 15 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new magento/community-edition vulnerabilities disclosed?

0 vulnerabilities were recorded for magento/community-edition in the last 12 months, and the oldest entry in this database dates to 12 Nov 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of magento/community-edition are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor magento/community-edition for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the magento/community-edition version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.