CVE-2016-4010

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-17. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 93%
CISA-KEV: Not listedEPSS: 93%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Magento CE and EE before 2.0.6 allows remote attackers to conduct PHP objection injection attacks and execute arbitrary PHP code via crafted serialized shopping cart data.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
86(Track*)
EG Risk 86/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation93% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
99.8%
KEV
Not listed

Published

January 23, 2017

Last Modified

May 13, 2026

Advisory Details (4)

Auto-updated Jun 24, 2026
No patch confirmed yet.
generic

Packet Storm

https://packetstormsecurity.com/files/137121/Magento-Unauthenticated-Arbitrary-File-Write.html
generic

Adobe Commerce release notes | Adobe Commerce

https://magento.com/security/patches/magento-206-security-update
generic

Magento – Unauthenticated Remote Code Execution – 0-Days And Life

http://netanelrub.in/2016/05/17/magento-unauthenticated-remote-code-execution/
generic🟡 PoC Available

Magento < 2.0.6 - Arbitrary Unserialize / Arbitrary Write File - PHP webapps Exploit

https://www.exploit-db.com/exploits/39838/

Data Freshness Timeline

(refreshed 4× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:23 UTCEG score recompute
  2. 2026-07-22 22:02 UTCEG score recompute
  3. 2026-07-19 02:26 UTCEPSS rescore
  4. 2026-07-19 02:26 UTCEPSS rescore
  5. 2026-07-13 22:26 UTCEPSS rescore
  6. 2026-07-12 05:43 UTCEPSS rescore
  7. 2026-07-12 05:43 UTCEPSS rescore
  8. 2026-07-11 08:23 UTCEPSS rescore
  9. 2026-07-09 19:05 UTCEPSS rescore
  10. 2026-07-08 06:57 UTCOSV refresh
  11. 2026-06-25 13:47 UTCEPSS rescore
  12. 2026-06-25 13:47 UTCEPSS rescore
  13. 2026-06-23 21:30 UTCEPSS rescore
  14. 2026-06-19 18:55 UTCOSV refresh
  15. 2026-06-17 17:50 UTCEPSS rescore
  16. 2026-06-17 17:50 UTCEPSS rescore
  17. 2026-06-15 17:45 UTCEPSS rescore
  18. 2026-06-14 23:14 UTCEPSS rescore
  19. 2026-06-13 22:57 UTCEPSS rescore
  20. 2026-06-13 22:57 UTCEPSS rescore
  21. 2026-06-12 23:09 UTCEPSS rescore
  22. 2026-06-12 23:09 UTCEPSS rescore
  23. 2026-06-11 13:57 UTCEPSS rescore
  24. 2026-06-10 22:15 UTCEPSS rescore
  25. 2026-06-05 22:44 UTCEPSS rescore
Show 27 more
  1. 2026-06-05 06:08 UTCEPSS rescore
  2. 2026-06-05 06:08 UTCEPSS rescore
  3. 2026-06-04 13:10 UTCEPSS rescore
  4. 2026-06-04 13:10 UTCEPSS rescore
  5. 2026-06-02 20:10 UTCEPSS rescore
  6. 2026-05-31 22:28 UTCEPSS rescore
  7. 2026-05-31 22:28 UTCEPSS rescore
  8. 2026-05-30 23:53 UTCOSV refresh
  9. 2026-05-28 13:42 UTCEPSS rescore
  10. 2026-05-28 13:42 UTCEPSS rescore
  11. 2026-05-27 13:38 UTCEPSS rescore
  12. 2026-05-27 13:38 UTCEPSS rescore
  13. 2026-05-26 07:16 UTCEPSS rescore
  14. 2026-05-22 21:15 UTCEPSS rescore
  15. 2026-05-22 21:15 UTCEPSS rescore
  16. 2026-05-20 09:27 UTCGHSA enrichment
  17. 2026-05-20 05:41 UTCGHSA enrichment
  18. 2026-05-20 01:55 UTCGHSA enrichment
  19. 2026-05-19 22:09 UTCGHSA enrichment
  20. 2026-05-19 18:23 UTCGHSA enrichment
  21. 2026-05-19 14:37 UTCGHSA enrichment
  22. 2026-05-19 10:51 UTCGHSA enrichment
  23. 2026-05-19 07:04 UTCGHSA enrichment
  24. 2026-05-19 03:18 UTCGHSA enrichment
  25. 2026-05-18 23:32 UTCEG score recompute
  26. 2026-05-18 21:30 UTCEPSS rescore
  27. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCshadofren/CVE-2016-4010
    First seen Aug 10, 2020

    CVE-2016-4010

    Open source ↗
  • GitHub PoCbrianwrf/Magento-CVE-2016-4010
    First seen May 25, 2016

    Magento Unauthorized Remote Code Execution (CVE-2016-4010)

    Open source ↗
  • Exploit-DBEDB-39838✓ verified
    First seen May 18, 2016

    Magento < 2.0.6 - Arbitrary Unserialize / Arbitrary Write File

    Open source ↗
  • Metasploitexploit/multi/http/magento_unserialize✓ verified
    First seen May 17, 2016

    Magento 2.0.6 Unserialize Remote Code Execution

    Open source ↗

Frequently asked(5)

What is CVE-2016-4010?
CVE-2016-4010 is a critical vulnerability published on January 23, 2017. Magento CE and EE before 2.0.6 allows remote attackers to conduct PHP objection injection attacks and execute arbitrary PHP code via crafted serialized shopping cart data.
When was CVE-2016-4010 disclosed?
CVE-2016-4010 was first published in the National Vulnerability Database on January 23, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-4010 actively exploited?
CVE-2016-4010 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-4010?
CVE-2016-4010 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2016-4010?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-4010, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2016-4010

Explore →

Is Your Infrastructure Affected by CVE-2016-4010?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs