Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDownload public VitaFit APK from Google Play
-
ExploitDecompile and locate hardcoded secrets
-
ExecutionExtract WeChat/QQ/Fitbit integration credentials
-
ImpactAbuse active third-party application registrations
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Credential externalization
MITRE ATT&CK
2 techniques across 2 tactics: Persistence, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires obtaining the publicly distributed VitaFit APK (com.vt.vitafit) from Google Play for any version before 2.8.1.0 and decompiling it to read the embedded hardcoded WeChat, Tencent QQ, and Fitbit integration secrets - the secrets ship in every copy, so no authentication, non-default configuration, or user interaction is needed. The practical limiting factor is that impact is confined to abuse of those third-party application registrations and is contingent on the exposed credentials still being valid; upgrading to 2.8.1.0 (and the vendor rotating the leaked secrets) removes the exposure. |
| Impact | The input CVSS 4.0 score of 8.7 (High) is driven by AV:N/AC:L/AT:N/PR:N/UI:N with a single confidentiality impact (VC:H) and no integrity or availability impact (VI:N/VA:N) and no scope change to subsequent systems - so the headline severity reflects easy, unauthenticated, network-reachable access rather than a destructive outcome. This is a CWE-798 hardcoded-credentials disclosure: the 'attack' is static analysis of a freely downloadable APK, which CVSS 4.0 rewards heavily because PR:N/UI:N/AV:N all apply, inflating the score relative to the actual harm (exposure of shared third-party integration secrets, not direct user-data compromise). No CISA KEV listing is present in the input and no EPSS probability was provided, so there is no signal of active or widespread exploitation; the vuln.today decision label is 'this_week', i.e. prompt but not emergency/act_now. A PoC exists only as a reference (a GitHub security-research repo) and is not verified as working exploit code. Signals are therefore broadly consistent - high-ease but confidentiality-only, moderate real-world urgency - with one data conflict: the 'Authentication Bypass' tag contradicts the CWE-798 hardcoded-credentials classification and the description, which describe secret disclosure, not an auth bypass. Real priority is moderate: triage within the week, but this is not an emergency and the downstream risk depends on whether the exposed WeChat/QQ/Fitbit registration secrets remain valid. |
| Exploit ScenarioDerived | An attacker downloads the free VitaFit app (com.vt.vitafit) from Google Play, decompiles the APK with standard tooling, and reads the hardcoded WeChat, Tencent QQ, and Fitbit integration secrets embedded in the code. With those secrets the attacker can abuse the vendor's active third-party application registrations. A public PoC reference exists; it is not verified as working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 04, 2026
Hardcoded third-party integration credentials in the VitaFit Android app before 2.8.1.0 expose embedded WeChat, Tencent QQ, and Fitbit application secrets to anyone who downloads the public APK and decompiles it, with no authentication or user interaction required. The impact is confidentiality-only and is contingent on the exposed credentials still being valid, limiting practical abuse to the associated third-party application registrations. A public PoC reference exists but is not verified as working exploit code, no CISA KEV confirmation of active exploitation is provided, and vuln.today assigns this_week priority.
RemediationAI
Vendor-released patch: 2.8.1.0. Upgrade VitaFit to version 2.8.1.0 or later through Google Play, and the vendor must rotate the leaked WeChat, Tencent QQ, and Fitbit integration secrets, because removing them from the APK does not invalidate copies already extracted from older versions; coordinate the rotation with the third-party platforms and invalidate the old application registrations where possible, planning for disruption to integrations that still depend on the old secrets. Older APKs should not be redistributed. The supplied references include the VulnCheck advisory at https://www.vulncheck.com/advisories/vitafit-android-hardcoded-credentials-disclosure and the research repository at https://github.com/je-lv/vitafit-security-research. No configuration-only workaround is described in the available data, and because the secrets ship in every copy, obfuscation or decompilation resistance would not be a complete fix-the complete remediation is the updated app plus secret rotation.
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
VitaFit is an Android health and fitness application distributed through Google Play under package com.vt.vitafit, with the affected CPE cpe:2.3:a:shenzhen_shine_industrial_co.,_ltd.:vitafit:*:*:*:*:*:*:*:*. The root cause is CWE-798, Use of Hard-coded Credentials: WeChat, Tencent QQ, and Fitbit integration secrets are compiled into the APK rather than being kept server-side or provisioned per installation. Because Android APKs are publicly downloadable and straightforward to decompile, static inspection of the package can recover those embedded values; this is a client-side secrets exposure, and the available sources do not describe any additional trigger, race condition, or memory-safety mechanism. The independently assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N matches a network-reachable, unauthenticated confidentiality-only issue with no integrity or availability impact. The supplied intelligence tags are Authentication Bypass, Google, and Vitafit.
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:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Secrets ship in a freely downloadable APK, so AV:N/AC:L/PR:N/UI:N; impact is pure disclosure of embedded credentials, hence C:H and I:N/A:N with unchanged scope.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
VitaFit Android application (com.vt.vitafit) before 2.8.1.0 contains a hardcoded credentials vulnerability that allows attackers to extract confidential third-party integration secrets by decompiling the APK. Attackers can retrieve embedded WeChat, Tencent QQ, and Fitbit credentials from the decompiled application to abuse the active third-party application registrations.
Articles & Coverage 1
Technical POC Analysis
CWE-798: Use of Hard-coded Credentials.
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
The VitaFit Android app before version 2.8.1.0 contains hardcoded credentials for WeChat, Tencent QQ, and Fitbit integrations, exposing these secrets to anyone who decompiles the publicly available APK. This affects users of the VitaFit app and could enable unauthorized access to third-party accounts or services if the credentials remain valid, posing a confidentiality risk to the organization's reputation and user trust. Leadership should prioritize remediation to prevent potential data breaches and compliance issues.
No vendor-released patch identified at time of analysis. Interim mitigations include: rotate or revoke any exposed WeChat, Tencent QQ, and Fitbit credentials immediately; monitor third-party service logs for unauthorized access; instruct users to update to the latest app version once available; and restrict access to the APK to trusted channels 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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
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
Insecure TLS certificate validation in the VitaFit Android app (com.vt.vitafit) before 2.8.1.0 lets an unauthenticated a
VitaFit Android before 2.8.1.0 exposes unencrypted m_session_id tokens in application backups, allowing anyone who obtai
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-117148
GHSA-25r7-r3v7-g6cq
NVD
CVE.org
EPSS
Exploit-DB