CVE-2013-6040 json
MW6 Aztec, DataMatrix, and MaxiCode ActiveX controls versions before 4.0 are vulnerable to arbitrary code via crafted HTML document.
published 12y ago modified 4mo ago also EUVD-2013-5870
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.4%
- EPSS 7.4% chance of exploitation in 30 days, percentile 94%
- public exploits
- 3
- Exploit-DB
Summary
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
Patch / fix
- MW6 Tech MW6 Aztec ActiveX Controls 4.0
- MW6 Tech MW6 DataMatrix ActiveX Controls 4.0
- MW6 Tech MW6 MaxiCode ActiveX Controls 4.0
Is CVE-2013-6040 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-31178)
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
7.37% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Affected products
- MW6 Tech MW6 Aztec ActiveX Controls
- MW6 Tech MW6 DataMatrix ActiveX Controls
- MW6 Tech MW6 MaxiCode ActiveX Controls
References
-
exploit-db.com
/exploits/31176
exploit
-
exploit-db.com
/exploits/31177
exploit
-
kb.cert.org
/vuls/id/219470
third-party-advisory, us-government-resource
- mw6tech.com
Sources
- CVE List CVE-2013-6040
- NVD CVE-2013-6040
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.