VitaFit Cloud API Excessive Data Exposure via relation/search Endpoint
Affects VitaFit before 2026-10-30 through the cloud API's relation/search endpoint, where an authenticated user can retrieve personal and health profile data for user records. No vendor rating or fix is listed in the checked facts.
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
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected product is VitaFit before 2026-10-30
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
CVE-2026-54383 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) 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? →
- 15/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? →
- Specific setups only
- 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, before 2026-10-30, exposes excessive user data through its relation/search endpoint. A remote attacker with only a basic authenticated account can enumerate the user directory and harvest personal and health-related profile details, including emails, phone numbers, birthdays, height, weight goals, and Firebase UIDs.
Read the original description
VitaFit cloud API before 2026-10-30 contained an excessive data exposure vulnerability that allows any authenticated user to query the GET /front/relation/search/ endpoint and retrieve PII and health-related profile information for user records. Attackers can enumerate the user directory using overlapping alphanumeric search terms to harvest identifiers, emails, birthdays, gender, height, weight goals, phone numbers, and Firebase UIDs.
What to do
Check whether your setup matches what the bug needs.
Affected product is VitaFit before 2026-10-30Upgrade 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-54383
Is CVE-2026-54383 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 relation/search endpoint of the VitaFit cloud API returns more data than it should. An authenticated user can retrieve PII and health-related profile information for user records, including identifiers, emails, birthdays, gender, height, weight goals, phone numbers, and Firebase UIDs.Source: vulncheck.com
Which versions are affected by CVE-2026-54383?
VitaFit: before 2026-10-30.Source: cve.now feed data
Am I affected, and how do I check?
The affected product is VitaFit before 2026-10-30. The checked facts do not describe a version command or setting for checking an installed build, so the release date is the only range given.Source: vulncheck.com
How do I fix CVE-2026-54383?
The checked facts do not name a fixed release or a workaround. The affected range ends at 2026-10-30, so that date is the boundary to check against.Source: vulncheck.com