CVE-2013-6223 json
LiveZilla before 5.1.1.0 stores the admin Base64 encoded username and password in a 1click file, which allows local users to obtain access…
published 12y ago modified 4mo ago also EUVD-2013-6052
- cvss
- 2.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
LiveZilla before 5.1.1.0 stores the admin Base64 encoded username and password in a 1click file, which allows local users to obtain access by reading the file.
Is CVE-2013-6223 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 FencerExploit prediction
0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- blog.curesec.com http://blog.curesec.com/article/blog/27.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-255 Credentials Management Errors
References
-
blog.curesec.com
/article/blog/27.html
exploit
-
forums.livezilla.net
/index.php?/topic/163-livezilla-changelog/
vendor-advisory
-
osvdb.org
/100400
vdb-entry
-
seclists.org
/fulldisclosure/2013/Nov/210
mailing-list
Sources
- CVE List CVE-2013-6223
- NVD CVE-2013-6223
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.