Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain app backup containing session data
-
ExploitExtract unencrypted m_session_id token
-
ExecutionReplay long-lived token to VitaFit server
-
ImpactRead, modify, or delete victim account
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V7 - Session Management Session expiration enforcement
|
| Exploitation Conditions | Exploitation requires the attacker to obtain the application's backup data (e.g., an Android/adb backup, an exported or cloud-synced backup, or device-level access) that contains the unencrypted m_session_id session token, for VitaFit Android versions before 2.8.1.0. Because the token remains valid for ten years, there is no session-expiry limit to prevent reuse once it is captured. The principal limiting factor is the LOCAL attack vector (CVSS AV:L): the flaw is not remotely exploitable over the network against a default configuration - the attacker must first gain access to the backup artifact. No in-app authentication or privileges are needed to use a stolen token (PR:N), and no user interaction is required. |
| Impact | Signals are mixed and point to a serious-but-not-remote-mass-exploitation issue. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:N, VC:H/VI:H/VA:H, score 8.6 High) is the decisive signal: the attack vector is LOCAL, meaning an attacker must first obtain the victim's application backup data to read the unencrypted m_session_id token - this is not a network-exploitable flaw against a listening service, so the 'High' rating reflects full account compromise once access is achieved, not easy remote reach. The vuln.today priority is 'this_week' (not act_now/emergency). There is NO CISA KEV listing (no confirmed active exploitation) and NO EPSS score was provided, so widespread opportunistic exploitation cannot be quantified from the input. A public PoC reference exists (VulnCheck/GitHub security research) but it is not verified as working exploit code, so POC availability should not be read as a weaponized exploit. The genuinely aggravating factor is the ten-year token lifetime (CWE-613): a single stolen token grants durable, long-lived account takeover with no expiry to limit reuse. Net: a real priority for affected users, warranting prompt patching, but its practical risk is gated by the need for local access to backup data rather than being a drive-by remote threat. |
| Exploit ScenarioDerived | An attacker who obtains a victim's Android backup (for example via adb backup, an exported/cloud backup, or direct device access) extracts the unencrypted m_session_id token and, because the token stays valid for ten years, replays it to fully control the victim's VitaFit account - reading and modifying data or deleting the authentication record to lock the owner out permanently. A public PoC reference exists but is not verified as working exploit code. The CVSS local attack vector (AV:L, AC:L) means the attacker needs access to the backup data rather than a purely remote network path. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 04, 2026
VitaFit Android before 2.8.1.0 exposes unencrypted m_session_id tokens in application backups, allowing anyone who obtains a backup to read and modify the victim's account or delete the authentication record and lock the owner out. Exploitation is local: the attacker must first obtain backup data containing the token, and no in-app authentication is required once it is captured; the token remains valid for ten years. A public PoC reference exists but is not verified as working exploit code, and there is no KEV confirmation of active exploitation.
RemediationAI
Vendor-released patch: 2.8.1.0 - update the VitaFit Android app to version 2.8.1.0 or later from the Google Play listing (https://play.google.com/store/apps/details?id=com.vt.vitafit). Consult the VulnCheck advisory (https://www.vulncheck.com/advisories/vitafit-android-long-lived-session-token-exposure) for vendor guidance. Because captured m_session_id tokens remain valid for ten years, updating should be paired with any vendor-provided token-revocation step for accounts whose backup data may have been exposed; the supplied sources do not describe a revocation mechanism. Where updating is not immediately possible, reduce exposure of backup artifacts that contain app data (adb backups, exported or cloud-synced backups) and limit device-level access, recognizing that this can affect backup/restore and data-portability workflows.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-613 (Insufficient Session Expiration) in the Android application com.vt.vitafit, whose m_session_id bearer token is stored unencrypted in application backups and remains valid for ten years. The CPE cpe:2.3:a:shenzhen_shine_industrial_co.,_ltd.:vitafit:*:*:*:*:*:*:*:* identifies the Shenzhen Shine Industrial Co., Ltd. VitaFit Android product, with versions before 2.8.1.0 affected. The assessed CVSS:3.1 vector is AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, reflecting that the trigger is acquisition of the backup artifact - an Android/adb backup, an exported or cloud-synced backup, or device-level access - rather than remote network access against a default configuration. Once the token is obtained, it can be replayed without in-app credentials to read or modify the account or delete the account's authentication record; the supplied sources do not describe an additional server-side or client-side control that limits reuse before the ten-year expiry.
Know when Vitafit gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Token sits in unencrypted local backups so access is local (AV:L) with no in-app privileges (PR:N); a stolen token enables full account read, modification, and authentication-record deletion, so C/I/A all High.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
VitaFit Android application (com.vt.vitafit) before 2.8.1.0 contains an insecure session management vulnerability that allows attackers to extract or intercept unencrypted m_session_id tokens stored in application backups, which remain valid for ten years. Attackers can use a stolen session token to read and modify the victim's account or delete the account's authentication record, preventing the legitimate owner from logging in again.
Articles & Coverage 1
Technical POC Analysis
CWE-613 (Insufficient Session Expiration), reported by the researcher as "Session Token with 10-Year Expiry Stored in Cleartext SharedPreferences", affecting "Android application and session service"…
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Latest POC
1 PoC candidate from github (unverified)
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
VitaFit Android versions before 2.8.1.0 store session authentication tokens in unencrypted backups, allowing anyone with access to a device backup to fully compromise user accounts, including modifying or deleting data and locking the legitimate owner out. This affects all VitaFit users on older app versions and requires immediate leadership attention due to the ten-year token lifespan and potential for widespread account takeovers.
No vendor-released patch identified at time of analysis. Interim mitigations: instruct users to disable cloud backups for the VitaFit app, enforce device encryption and strong screen locks, and monitor for unauthorized account activity. Restrict backup access to trusted devices only.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
VitaFit's cloud API before 2026-10-30 would issue a full authenticated session for any account whose linked Google or Fa
Broken access control in the VitaFit cloud API before the 2026-10-30 fix lets any authenticated account holder call POST
VitaFit's cloud API left its backing object storage bucket readable by anyone, so an attacker who locates the bucket can
Hardcoded third-party integration credentials in the VitaFit Android app before 2.8.1.0 expose embedded WeChat, Tencent
Insecure TLS certificate validation in the VitaFit Android app (com.vt.vitafit) before 2.8.1.0 lets an unauthenticated a
Token interception in VitaFit Android before 2.8.1.0 allows a malicious app already installed on the device to register
The VitaFit cloud API, in builds prior to the 2026-10-30 release, returns other users' personally identifiable and healt
Authenticated users of the VitaFit fitness and smart-scale cloud API can read other accounts' data - email address, prof
An improper access control flaw in the VitaFit cloud API let authenticated holders of Cognito-issued AWS credentials wri
Stored cross-site scripting in the VitaFit cloud API (builds before 2026-10-30) lets an authenticated account holder upl
Cleartext HTTP handling in the VitaFit Android app (com.vt.vitafit) before 2.8.1.0 lets an attacker who holds a man-in-t
EUVD-2026-117149
GHSA-5fv5-qp4h-7jpg
NVD
CVE.org
EPSS
Exploit-DB