CVE-2016-6545: Session cookies are not used for maintaining valid sessions in iTrack Easy
CVE-2016-6545 is a critical-severity flaw (CVSS 9.8) affecting itrackeasy. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Session cookies are not used for maintaining valid sessions in iTrack Easy. The user's password is passed as a POST parameter over HTTPS using a base64 encoded passwd field on every request. In this implementation, sessions can only be terminated when the user changes the associated password.
Why this priority
- Critical severity
- Remotely exploitable, no login, no user action
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-6545?
itrackeasy: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2016-6545 being exploited?
CVE-2016-6545 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-6545 affect?
CVE-2016-6545 affects itrackeasy. Severity is critical (CVSS 9.8). Session cookies are not used for maintaining valid sessions in iTrack Easy. The user's password is passed as a POST parameter over HTTPS using a base64 encoded passwd field on every request. In this implementation, sessions can only be term
How urgent is CVE-2016-6545?
Priority 61/100. Critical severity; Remotely exploitable, no login, no user action
Related CVEs
- CVE-2016-6546 HIGH 7.8 MITIGATE The iTrack Easy mobile application stores the account password used to authenticate to the cloud API in base64
- 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