VitaFit Cloud API Authentication Bypass via POST /front/login/sns/
Affects VitaFit cloud API builds before 2026-10-30 where accounts are linked to Google or Facebook SNS login. CVSS rates it critical; no vendor rating is given. Fixed in 2026-10-30.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026-10-30
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2026-10-30.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Data gap: Advisories don't say whether default setups are affected
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
CVE-2026-54384 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects VitaFit; fixed in 2026-10-30.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 2026-10-30
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
VitaFit's cloud API contains an authentication bypass in its POST /front/login/sns/ endpoint that lets a remote attacker, without logging in, obtain a full session for a victim's account using a linked Google or Facebook identifier without proving ownership of it. An attacker can use this to read and modify the victim's profile and delete the account's authentication record, locking the legitimate user out.
Read the original description
VitaFit cloud API before 2026-10-30 contained an authentication bypass vulnerability that allows remote attackers to obtain a full session for a victim's account by submitting a linked Google or Facebook account identifier to the POST /front/login/sns/ endpoint without providing proof of ownership from the identity provider. Attackers can forge a login using an identifier exposed through account enumeration to read and modify the victim's profile and delete the account's authentication record, preventing the legitimate user from logging in.
What to do
Upgrade to a fixed version: 2026-10-30.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Shenzhen Shine Industrial Co., Ltd. VitaFit
fixed in 2026-10-30
Evidence 3
- Exploit
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-54384
Is CVE-2026-54384 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The POST /front/login/sns/ endpoint accepts a linked Google or Facebook account identifier without proper authentication, so a remote attacker can obtain a full session for a victim's account. The attacker can also read and modify the victim's profile and delete the account's authentication record, locking out the legitimate user.Source: vulncheck.com
Which versions are affected by CVE-2026-54384?
VitaFit: before 2026-10-30.Source: cve.now feed data
Am I affected, and how do I check?
Builds of the VitaFit cloud API before 2026-10-30 are affected, and only for accounts linked to a Google or Facebook SNS identifier. The attacker needs such an identifier, which account enumeration can expose. Check whether the deployed cloud API predates 2026-10-30 and whether accounts use Google or Facebook SNS login.Source: vulncheck.com
How do I fix CVE-2026-54384?
Update the VitaFit cloud API to the 2026-10-30 build or later. The facts give no workaround, so the update is the fix.Source: vulncheck.com