Vulnerability Database · Packagist · Package report

ec-cube/ec-cube: vulnerability history, versions and safety

ec-cube/ec-cube is a package in the Packagist ecosystem. Vulert records 15 vulnerabilities for it across 77 releases, from Nov 2021 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
15 vulnerabilities recorded H2 M12 L1
i
9 with no fix published

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

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

Most recent disclosure 05 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on ec-cube/ec-cube i

Updated on 23 Oct 2026

Careful: 9 of the 15 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 15 vulnerabilities on record across 4 years, 1 in the last year.

What to do: Plan around the 9 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 15 over 4 years · 1 in the last year i
  • Latest disclosure 05 Mar 2026 i
  • Highest CVSS 8.1 i
  • With no published fix 9 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 ec-cube/ec-cube, 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
4.3.1 M1 No Details →
4.3.0 M1 No Details →
4.3.0-rc M1 No Details →
4.3.0-beta-20240530 M1 No Details →
4.3.0-beta-240412 M1 No Details →
4.3.0-beta M1 No Details →
4.3.0-alpha-0304 M1 No Details →
4.3.0-alpha M1 No Details →
4.2.3-p2 M1 No Details →
4.2.3-p1 M1 No Details →
4.2.3 M1 No Details →
4.2.2 M1 No Details →
4.2.1 M1 No Details →
4.2.0 M1 No Details →
4.2.0-rc M1 No Details →
4.2.0-beta-20220802 M1 No Details →
4.2.0-beta-20220722 M1 No Details →
4.2.0-beta-20220630 M1 No Details →
4.2.0-beta2-20220916 M1 No Details →
4.2.0-beta2-20220905 M1 No Details →
4.2.0-beta2-20220829 M1 No Details →
4.2.0-beta2-20220826 M1 No Details →
4.2.0-beta2-20220825 M1 No Details →
4.2.0-beta2-20220824 M1 No Details →
4.2.0-beta2-20220810 M1 No Details →
4.2.0-beta2 M1 No Details →
4.2.0-beta M1 No Details →
4.2.0-alpha M1 No Details →
4.1.2-p5 M1 No Details →
4.1.2-p4 M1 No Details →
4.1.2-p3 M1 No Details →
4.1.2-p2 M1 No Details →
4.1.2-p1 M1 No Details →
4.1.2 M2 No Details →
4.1.1 M2 No Details →
4.1.0 M2 No Details →
4.1-rc M1 No Details →
4.1-beta3-20210903 M1 No Details →
4.1-beta3-20210901 M1 No Details →
4.1-beta3-20210831 M1 No Details →
4.1-beta3 M1 No Details →
4.1-beta2 M1 No Details →
4.1-beta M1 No Details →
4.0.6-p4 M1 No Details →
4.0.6-p3 M1 No Details →
4.0.6-p2 M1 No Details →
4.0.6-p1 M1 No Details →
4.0.6 M1 No Details →
4.0.5-p1 M2 No Details →
4.0.5 M3 No Details →
4.0.5-rc M3 No Details →
4.0.4 M3 No Details →
4.0.3 M3 No Details →
4.0.2 M3 No Details →
4.0.1 M3 No Details →
4.0.0 M3 No Details →
3.0.18 H2 M3 L1 No Details →
3.0.17 H2 M3 L1 No Details →
3.0.16 H2 M4 L1 No Details →
3.0.15 H2 M4 L1 No Details →
3.0.14 H2 M4 L1 No Details →
3.0.13 H2 M4 L1 No Details →
3.0.12-p1 H2 M4 L1 No Details →
3.0.12 H2 M4 L1 No Details →
3.0.11 H2 M4 L1 No Details →
3.0.11-RC H2 M4 L1 No Details →
3.0.10 H2 M4 L1 No Details →
3.0.9 H2 M4 L1 No Details →
3.0.8 H2 M4 L1 No Details →
3.0.7 H2 M4 L1 No Details →
3.0.6 H2 M4 L1 No Details →
3.0.5 H2 M4 L1 No Details →
3.0.4 H1 M4 L1 No Details →
3.0.3 H1 M4 L1 No Details →
3.0.2 H1 M4 L1 No Details →
3.0.1 H1 M4 L1 No Details →
3.0.0 H1 M4 L1 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 13
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for ec-cube/ec-cube

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 in the database →

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 ec-cube/ec-cube

Is ec-cube/ec-cube safe to use?

Vulert records 15 vulnerabilities for ec-cube/ec-cube in Packagist: 0 critical, 2 high, 12 medium and 1 low. 9 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does ec-cube/ec-cube have?

15 vulnerabilities are recorded for ec-cube/ec-cube in the Packagist ecosystem: 0 critical, 2 high, 12 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ec-cube/ec-cube vulnerabilities disclosed?

1 vulnerability was recorded for ec-cube/ec-cube in the last 12 months, and the oldest entry in this database dates to 25 Nov 2021. 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 ec-cube/ec-cube 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 ec-cube/ec-cube for upcoming vulnerabilities?

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