CVE-2013-6040

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 7%CVSS: 8.1Exploit: NoneExposed: 0

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

MW6 Aztec, DataMatrix, and MaxiCode ActiveX controls before version 4.0 vulnerable to arbitrary code via a crafted HTML document. Latest versions (4.0) of MW6 Aztec, DataMatrix, and MaxiCode ActiveX controls have resolved the issue

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
93.7%
KEV
Not listed

Published

January 21, 2014

Last Modified

April 29, 2026

Advisory Details (4)

Auto-updated Apr 30, 2026
🔬 Proof of concept available. No patch confirmed yet. Sources: cert.
cert

VU#219470 - MW6 Technologies ActiveX controls contain multiple vulnerabilities

http://www.kb.cert.org/vuls/id/219470
generic🟡 PoC Available

MW6 Technologies Datamatrix - ActiveX 'Data' Buffer Overflow - Windows dos Exploit

http://www.exploit-db.com/exploits/31177
generic🟡 PoC Available

MW6 Technologies Aztec - ActiveX 'Data' Buffer Overflow (PoC) - Windows dos Exploit

http://www.exploit-db.com/exploits/31176
generic

MW6 Technologies, Inc. ::: 1 Passion 4 0's + 1's

https://www.mw6tech.com

Data Freshness Timeline

(refreshed 8× in last 7d / 37× 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-07 13:41 UTCEPSS rescore
  2. 2026-07-06 02:20 UTCEPSS rescore
  3. 2026-07-06 02:19 UTCEPSS rescore
  4. 2026-07-05 02:26 UTCEPSS rescore
  5. 2026-07-04 06:27 UTCEPSS rescore
  6. 2026-07-02 15:21 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-29 14:02 UTCEPSS rescore
  10. 2026-06-28 14:03 UTCEPSS rescore
  11. 2026-06-28 04:53 UTCEPSS rescore
  12. 2026-06-28 04:53 UTCEPSS rescore
  13. 2026-06-27 03:05 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-24 14:02 UTCEPSS rescore
  17. 2026-06-24 14:02 UTCEPSS rescore
  18. 2026-06-23 21:30 UTCEPSS rescore
  19. 2026-06-23 21:30 UTCEPSS rescore
  20. 2026-06-22 14:22 UTCEPSS rescore
  21. 2026-06-22 14:22 UTCEPSS rescore
  22. 2026-06-19 19:23 UTCEPSS rescore
  23. 2026-06-18 17:49 UTCEPSS rescore
  24. 2026-06-18 17:49 UTCEPSS rescore
  25. 2026-06-17 17:49 UTCEPSS rescore
Show 51 more
  1. 2026-06-17 17:49 UTCEPSS rescore
  2. 2026-06-16 17:49 UTCEPSS rescore
  3. 2026-06-16 17:49 UTCEPSS rescore
  4. 2026-06-16 17:49 UTCEPSS rescore
  5. 2026-06-15 17:44 UTCEPSS rescore
  6. 2026-06-14 23:14 UTCEPSS rescore
  7. 2026-06-13 22:57 UTCEPSS rescore
  8. 2026-06-12 23:08 UTCEPSS rescore
  9. 2026-06-11 13:56 UTCEPSS rescore
  10. 2026-06-10 22:15 UTCEPSS rescore
  11. 2026-06-10 13:18 UTCEPSS rescore
  12. 2026-06-08 14:14 UTCEPSS rescore
  13. 2026-06-07 15:22 UTCEPSS rescore
  14. 2026-06-06 13:45 UTCEPSS rescore
  15. 2026-06-06 13:45 UTCEPSS rescore
  16. 2026-06-05 22:44 UTCEPSS rescore
  17. 2026-06-05 22:44 UTCEPSS rescore
  18. 2026-06-05 06:08 UTCEPSS rescore
  19. 2026-06-05 06:08 UTCEPSS rescore
  20. 2026-06-04 13:09 UTCEPSS rescore
  21. 2026-06-04 13:09 UTCEPSS rescore
  22. 2026-06-02 20:10 UTCEPSS rescore
  23. 2026-06-02 20:10 UTCEPSS rescore
  24. 2026-06-01 13:49 UTCEPSS rescore
  25. 2026-06-01 13:49 UTCEPSS rescore
  26. 2026-05-31 22:28 UTCEPSS rescore
  27. 2026-05-31 22:28 UTCEPSS rescore
  28. 2026-05-31 00:14 UTCEPSS rescore
  29. 2026-05-31 00:14 UTCEPSS rescore
  30. 2026-05-29 13:41 UTCEPSS rescore
  31. 2026-05-29 13:41 UTCEPSS rescore
  32. 2026-05-28 20:44 UTCEG score recompute
  33. 2026-05-28 20:44 UTCGHSA enrichment
  34. 2026-05-28 13:42 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-28 13:42 UTCEPSS rescore
  37. 2026-05-27 13:38 UTCEPSS rescore
  38. 2026-05-27 13:38 UTCEPSS rescore
  39. 2026-05-26 13:41 UTCEPSS rescore
  40. 2026-05-26 13:41 UTCEPSS rescore
  41. 2026-05-24 16:43 UTCEPSS rescore
  42. 2026-05-22 21:15 UTCEPSS rescore
  43. 2026-05-22 21:15 UTCEPSS rescore
  44. 2026-05-22 21:15 UTCEPSS rescore
  45. 2026-05-21 22:39 UTCEPSS rescore
  46. 2026-05-20 22:37 UTCEPSS rescore
  47. 2026-05-20 22:37 UTCEPSS rescore
  48. 2026-05-20 11:21 UTCEPSS rescore
  49. 2026-05-20 11:21 UTCEPSS rescore
  50. 2026-05-18 21:29 UTCEPSS rescore
  51. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(3 references)

Working exploit code is in the public domain (3 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-31176
    First seen Jan 24, 2014

    MW6 Technologies Aztec - ActiveX 'Data' Buffer Overflow (PoC)

    Open source ↗
  • Exploit-DBEDB-31177
    First seen Jan 24, 2014

    MW6 Technologies Datamatrix - ActiveX 'Data' Buffer Overflow

    Open source ↗
  • Exploit-DBEDB-31178
    First seen Jan 24, 2014

    MW6 Technologies MaxiCode - ActiveX 'Data' Buffer Overflow (PoC)

    Open source ↗

Frequently asked(5)

What is CVE-2013-6040?
CVE-2013-6040 is a high vulnerability published on January 21, 2014. MW6 Aztec, DataMatrix, and MaxiCode ActiveX controls before version 4.0 vulnerable to arbitrary code via a crafted HTML document. Latest versions (4.0) of MW6 Aztec, DataMatrix, and MaxiCode ActiveX controls have resolved the issue
When was CVE-2013-6040 disclosed?
CVE-2013-6040 was first published in the National Vulnerability Database on January 21, 2014, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-6040 actively exploited?
CVE-2013-6040 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 93.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2013-6040?
CVE-2013-6040 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2013-6040?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-6040, 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-2013-6040

Explore →

Is Your Infrastructure Affected by CVE-2013-6040?

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