IZON IP 2.0.2: hard-coded password vulnerability

published 2020-02-12 6y ago modified 2026-06-17 4mo ago also EUVD-2013-6064

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 10.2%; EPSS 10.2% chance of exploitation in 30 days, percentile 95%
public exploits: 1; Exploit-DB

Is CVE-2013-6236 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 Fencer

Timeline

2013-10-29 First public exploit (EDB-29266)
2020-02-12 Published

Exploit prediction

10.21% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

EDB-29266 Stem Innovation - 'IZON' Hard-Coded Credentials webapps, 2013-10-29
seclists.org https://seclists.org/bugtraq/2013/Oct/149 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	10.0	AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness

CWE-798 Use of Hard-coded Credentials

References

seclists.org /bugtraq/2013/Oct/149
exploit, mailing-list, third-party-advisory
exchange.xforce.ibmcloud.com /vulnerabilities/88337
third-party-advisory, vdb-entry
packetstormsecurity.com /files/cve/CVE-2013-6236
third-party-advisory, vdb-entry

Sources

CVE List CVE-2013-6236
NVD CVE-2013-6236

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.