On this page (6 sections)

CVE-2026-54384 describes a critical authentication bypass in the VitaFit cloud API. According to the NVD record, a remote attacker could get a full session for someone else's account by sending that person's linked Google or Facebook account identifier to the social login endpoint, without any proof from the identity provider.

VitaFit users should care, and so should anyone who builds or runs a site or app with a "Sign in with Google/Facebook" feature. The mistake behind this CVE is a general one, and it is worth checking your own login code for it.

What happened

The NVD record says the VitaFit cloud API, in versions before 2026-10-30, accepted a login request at the POST /front/login/sns/ endpoint that carried only a linked Google or Facebook account identifier. The service did not require the identity provider to confirm that the requester actually owned that account.

The record adds that the identifier could be learned through account enumeration, meaning the API gave away enough information to find valid identifiers. With a valid identifier, an attacker could forge a login, read and modify the victim's profile, and delete the account's authentication record. Removing that record would stop the real owner from logging in.

The CVE was published on 2026-11-04. The record points to a researcher repository on GitHub and a VulnCheck advisory. Only one independent publisher covers this story so far, so treat details beyond the NVD text as unverified.

Why this class of bug is dangerous

Social login normally works because the identity provider vouches for the user. The app receives a signed token or a one-time code, checks it with the provider, and only then trusts the account identifier inside it. The flaw described here is what happens when the server skips that check and trusts an identifier sent by the client.

An account identifier is a label, not a secret. Anyone who learns it can claim it if the server never asks for proof. That is why the record pairs the bypass with account enumeration: the first problem reveals the labels, the second lets an attacker use them.

The impact goes beyond reading data. Because the attacker could delete the authentication record, the victim could lose access to their own account, which turns a privacy problem into an account takeover with lockout.

Who is affected

  • VitaFit account holders whose accounts were linked to Google or Facebook. The record does not say whether accounts using only other sign-in methods were affected, so do not assume either way.
  • Anyone whose VitaFit data may have been viewed or changed before the fix. The research does not say whether this happened.
  • Developers and agencies running their own sign-in flows. The VitaFit code is not yours, but the same design error can exist in custom OAuth or SSO integrations.

The research does not give a fix version number, only that the API before 2026-10-30 was affected. Because this is a hosted cloud API, the fix would normally be applied by the vendor on the server side, but the research does not confirm what VitaFit changed or whether users must do anything. Check the vendor's own communications and the VulnCheck advisory for updates.

What to do now

If you are a VitaFit user

  1. Open the VitaFit app or account page and confirm you can still sign in. A sudden inability to log in could be a sign of the lockout described in the record.
  2. Review your profile details for changes you did not make.
  3. Update the app from its Google Play listing if an update is offered.
  4. Review which apps are connected to your Google and Facebook accounts and remove any you do not recognize.
  5. Watch for official notices from VitaFit, and be cautious about emails that ask you to click a link to "secure" your account.

If you build or run a site with social login

Use this as a review checklist for your own code. Nothing here is specific to VitaFit, and none of it depends on the details of the vulnerable endpoint.

  1. Verify every sign-in with the provider. Validate the ID token signature, issuer, audience and expiry, or exchange the authorization code server-side. Never accept a bare user identifier from the client.
  2. Create the session only after that verification succeeds, and tie it to the identity the provider confirmed.
  3. Make login and sign-up responses identical for known and unknown accounts so identifiers cannot be enumerated.
  4. Rate limit and log login attempts, and alert on bursts of attempts against many different identifiers.
  5. Never let a single request delete the only way a user can sign in. Require recent re-authentication for credential changes and account deletion.
  6. Add an automated test that sends a login request with an identifier but no valid provider proof and expects a rejection.
Tip. If you are unsure whether your integration verifies tokens correctly, ask a developer to read the login handler and confirm it calls the provider's verification step before issuing any session.

Detection and monitoring

For your own applications, look in access logs for repeated POST requests to login endpoints from the same address using many different identifiers, and for successful logins that have no matching callback from the identity provider. Also watch for accounts whose sign-in method disappears or changes unexpectedly, and for support requests from users who say they are suddenly locked out.

Outside-in checks cannot see inside an API's authentication logic, so they will not tell you whether a login flow is sound. They can still help with the surrounding basics, such as security headers and certificate health, and monitoring can alert you when certificates or headers change unexpectedly. Our guide on small business website security covers the broader habits.

What we do not know yet

  • Whether the flaw was exploited in the wild. The CVE record shows no CISA KEV entry, and the research contains no exploitation reports.
  • How many accounts, if any, were accessed or locked out.
  • Exactly how VitaFit fixed the problem, or whether users need to take any action.
  • Whether VitaFit has published its own advisory. The research includes only the NVD record and references to third-party pages.

We will treat the details as provisional until the vendor or additional independent sources confirm them.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-54384: 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…nvd.nist.gov ·
  • CVE-2026-54384
  • VitaFit
  • authentication bypass
  • social login
  • API security