CVE-2016-6546: The iTrack Easy mobile application stores the account password used to authenticate to the cloud API in base64
CVE-2016-6546 is a high-severity flaw (CVSS 7.8) affecting itrackeasy. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The iTrack Easy mobile application stores the account password used to authenticate to the cloud API in base64-encoding in the cache.db file. The base64 encoding format is considered equivalent to cleartext.
Why this priority
- High severity
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2016-6546?
itrackeasy: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2016-6546 being exploited?
CVE-2016-6546 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2016-6546 affect?
CVE-2016-6546 affects itrackeasy. Severity is high (CVSS 7.8). The iTrack Easy mobile application stores the account password used to authenticate to the cloud API in base64-encoding in the cache.db file. The base64 encoding format is considered equivalent to cleartext.
How urgent is CVE-2016-6546?
Priority 41/100. High severity; Public exploit reference
Related CVEs
- CVE-2016-6545 CRITICAL 9.8 MITIGATE Session cookies are not used for maintaining valid sessions in iTrack Easy
- CVE-2016-6542 LOW 3.7 MITIGATE The iTrack device tracking ID number, also called "LosserID" in the web API, can be obtained by being in the r