How severe is CVE-2021-20842?

CVE-2021-20842 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-20842?

CVE-2021-20842 affects the following packages: ec-cube/ec-cube (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2021-20842?

Update ec-cube/ec-cube to 2.17.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-20842 is resolved across your whole dependency graph.

How do I detect CVE-2021-20842 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ec-cube/ec-cube, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-20842 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2021-20842 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2021-20842, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2021-20842?

CVE-2021-20842 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 46th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-20842?

CVE-2021-20842 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-20842 published, and has it been updated?

CVE-2021-20842 was published on November 24, 2021 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2021-20842 — ec-cube

MEDIUM

CVE-2021-20842 is a medium-severity (CVSS 6.5) Cross-Site Request Forgery (CSRF) vulnerability in ec-cube/ec-cube. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for ec-cube/ec-cube — see the affected versions and patch details below.

EC-CUBE Cross-site request forgery (CSRF) vulnerability

Also known asGHSA-m9hv-qmqh-33qh

Published

Nov 24, 2021

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘ec-cube/ec-cube

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Cross-site request forgery (CSRF) vulnerability in EC-CUBE 2 series 2.11.0 to 2.17.1 allows a remote attacker to hijack the authentication of Administrator and delete Administrator via a specially crafted web page.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ec-cube/ec-cube`	≥ 2.11.0&&< 2.17.2	2.17.2`composer require ec-cube/ec-cube:^2.17.2`

Affected Products

1 product · 1 configurations

Application

ec-cubeec-cube

≥ 2.11.0 && ≤ 2.17.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Cross-site request forgery (CSRF) vulnerability in EC-CUBE 2 series 2.11…

ec-cube.netNVDNov 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ec-cube/ec-cube, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ec-cube/ec-cube to 2.17.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-20842 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2021-20842 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

CWE Classification

CWE-352Cross-Site Request Forgery (CSRF)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

ec-cube

6.6/10

Code-Review10/10

Maintained10/10

Branch-ProtectionN/A

Assessed Nov 2, 2026

Timeline

Disclosed

Nov 24, 2021

First exploit

Nov 27, 2021

2 days after disclosure — rapid exploitation

Last updated

Oct 24, 2026

Identifiers

CVE-2021-20842

GHSA-m9hv-qmqh-33qh

References

Advisoryjvn.jp · index Advisorynvd.nist.gov · CVE 2021 20842 Fixec-cube.net Webec-cube.net Packagegithub.com · ec cube

Related vulnerabilities

This CVE is medium severity; 7 of 8 other CVEs affecting ec-cube/ec-cube are rated as high or higher (top: high).

GHSA-7rhv-h82h-vpjhCVE-2022-38975CVE-2022-40199CVE-2020-5680CVE-2021-20717CVE-2020-5590CVE-2021-20751CVE-2020-5679

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2021-20842 — ec-cube

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2021-20842 in your dependencies?