VitaFit Cloud API IDOR via profile_id Endpoints
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
- Exposure?/25Exposure: unknown (data gap). No advisory context yet
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
CVE-2026-54377 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) 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? →
- 7/100 · provisional
- 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 has an insecure direct object reference flaw that lets a local attacker, without logging in, read other users' email addresses, profiles, body-composition reports, and measurement history by changing the user or profile ID in endpoints such as /front/profile/{profile_id}/report/. Predictable IDs and an account-enumeration weakness let attackers do this at scale.
Read the original description
VitaFit cloud API before 2026-10-30 contained an insecure direct object reference vulnerability that allows authenticated attackers to access another user's data by supplying a different user_id or profile_id to endpoints such as GET /front/profile/{profile_id}/report/ and GET /front/profile/{profile_id}/body_index_per_day/. Attackers can leverage predictable user_id and profile_id relationships combined with an account-enumeration weakness to read another account's email address, profile, body-composition report, and measurement history at scale.
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-54377
Is CVE-2026-54377 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
Which versions are affected by CVE-2026-54377?
VitaFit: before 2026-10-30.Source: cve.now feed data
How do I fix CVE-2026-54377?
Upgrade to a fixed version: 2026-10-30.Source: cve.now feed data