Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister/authenticate to VitaFit cloud API
-
DeliveryCall POST /front/user/s3/token/ endpoint
-
ExploitReceive over-scoped temporary AWS credentials
-
ExecutionList shared S3 bucket
-
ImpactRead or overwrite other users' files
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V6 - Authentication Credential protection in transit/storage
|
| Exploitation Conditions | Requires a valid authenticated VitaFit cloud account (PR:L); because the app offers normal user self-registration, this prerequisite is trivially satisfied by any attacker. The attacker then calls the specific endpoint POST /front/user/s3/token/, which returns improperly scoped temporary AWS credentials usable against the shared storage bucket. No special non-default configuration, no user interaction, and no victim action are needed; exploitation works against the cloud service as deployed prior to the 2026-10-30 fix. The only meaningful limiting factor is the need for an authenticated account and reachability of the cloud API. |
| Impact | This is a genuine high-priority issue, not a CVSS-inflated one. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) describes a network-reachable, low-complexity flaw requiring only a single low-privilege authenticated account - and because VitaFit is a consumer fitness app with self-service registration, PR:L is a very low bar for any attacker. The scored impact (VC:H/VI:H and subsequent-system SC:H/SI:H) reflects that improperly scoped AWS credentials grant read and overwrite access across the shared bucket, affecting other users' data (a scope-changing, confidentiality- and integrity-breaking condition; no availability impact is claimed, consistent with VA:N/SA:N). The vuln.today Decision label is act_now, and the issue was reported by VulnCheck, which raises credibility. Signals that temper urgency: this is NOT listed in CISA KEV, no EPSS exploitation-probability score was provided, and the public PoC is a GitHub research reference that is not verified as working exploit code. So exploitation is assessed as a strong, low-effort possibility backed by a published advisory and research repo, but there is no evidence of active in-the-wild exploitation at time of analysis. |
| Exploit ScenarioDerived | An attacker registers or uses any ordinary VitaFit account, authenticates to the cloud API, and calls POST /front/user/s3/token/ to receive temporary AWS credentials that are scoped too broadly. Using those credentials they list the shared storage bucket and read or overwrite files belonging to other users, achieving cross-user data theft and tampering. A public PoC reference exists (a VulnCheck/GitHub security-research repo); 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
Broken access control in the VitaFit cloud API before the 2026-10-30 fix lets any authenticated account holder call POST /front/user/s3/token/ and receive temporary AWS credentials that are not scoped to that user's own storage, so an attacker can enumerate the shared bucket and read or overwrite other users' files. The authentication prerequisite is weak in practice: because the mobile app (com.vt.vitafit) allows normal self-registration, the PR:L requirement in the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N) is trivially satisfied, and no victim action or special configuration is needed against cloud deployments prior to the fix. Impact is high on both confidentiality and integrity with no availability effect; a public PoC reference exists at the researcher's GitHub repository, but it is not verified as working exploit code, and no CISA KEV listing or active-exploitation confirmation accompanies this CVE.
RemediationAI
The defect is server-side and was corrected in the VitaFit cloud API as of 2026-10-30, so the complete fix is to confirm the deployment is running a build from that date or later; no separate client patch and no discrete version number were published, so the date boundary in the advisory (https://www.vulncheck.com/advisories/vitafit-cloud-api-broken-access-control-via-s3-token-endpoint) is the authoritative marker. Operators that cannot immediately verify the backend build should treat every pre-2026-10-30 deployment as exposed, because the vendored credentials are only as strong as their IAM scope - the durable server-side correction is to bind issued credentials to the authenticated principal and to a per-user key prefix rather than to the shared bucket. Customer-side workarounds are not documented in the available sources, so the practical interim actions are detective rather than preventive: review S3 access logs for POST /front/user/s3/token/ callers whose subsequent GetObject or PutObject activity crosses user-prefix boundaries, rotate or invalidate any long-lived credentials issued before the fix, and restrict self-registration if the tenant model does not yet enforce per-user object authorization. Each of these has trade-offs - log review only detects after the fact, credential rotation can disrupt active sessions, and disabling self-registration blocks legitimate new users - none restores the per-object authorization guarantee that the 2026-10-30 update provides.
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 classified as CWE-522 (Insufficiently Protected Credentials) and manifests as a broken access-control decision on a credential-minting endpoint rather than as a memory-safety or parsing bug. The VitaFit cloud API exposes POST /front/user/s3/token/, which brokers access to S3 storage; instead of issuing credentials bound to the requesting identity, or to a per-user key prefix, it returns STS-style temporary AWS credentials whose IAM policy grants bucket-level reach over the shared storage bucket. Because the credentials are improperly scoped, knowledge of the endpoint is sufficient to pivot from a single low-privilege account onto every other tenant's objects in that bucket, producing cross-user read and overwrite. The CPE string cpe:2.3:a:shenzhen_shine_industrial_co.,_ltd.:vitafit:*:*:*:*:*:*:*:* identifies the affected product family, and the published Google Play entry for com.vt.vitafit is the client that authenticates to the vulnerable backend. The exact trigger preconditions are established in the advisory and research write-up: a valid account plus network reachability of the cloud API; the sources do not describe any further conditions such as a specific tenant tier or non-default setting.
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:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
Any self-registered authenticated user (PR:L) calls a network API with no interaction; over-scoped credentials reach other users' data in a separate storage system (S:C) with high confidentiality and integrity impact, no availability loss.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
VitaFit cloud API before 2026-10-30 contained a broken access control vulnerability that allows any authenticated user to obtain temporary AWS credentials by calling the POST /front/user/s3/token/ endpoint. Attackers can use these improperly scoped credentials to list the shared storage bucket and read or overwrite other users' stored files, enabling unauthorized cross-user data access and manipulation.
Technical POC Analysis
The defect is CWE-522 Insufficiently Protected Credentials in the VitaFit cloud API.
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 cloud API contains a critical access control flaw that permits any registered user to obtain temporary AWS credentials granting access to other users' storage, affecting all customers using the VitaFit mobile app prior to the 2026-10-30 fix. This exposes sensitive customer data to unauthorized reading and tampering, creating significant regulatory, reputational, and financial risk for the organization.
No vendor-released patch identified at time of analysis; interim mitigations include restricting API endpoint access, monitoring for abuse of temporary credentials, and enforcing S3 bucket policies that require user-specific prefixes.
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
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
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-117155
GHSA-jr4h-546g-564w
NVD
CVE.org
EPSS
Exploit-DB