# CVE-2021-36460: Auth bypass in n/a

> An attacker with a stolen local password hash can take over user accounts because the app uses the hash directly for backend authentication.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Apr 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-4jxf-pjgf-g7fc

## What is CVE-2021-36460?

CVE-2021-36460 is a high-severity authentication bypass vulnerability in n/a, published on 25 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

VeryFitPro (com.veryfit2hr.second) 3.2.8 hashes the account's password locally on the device and uses the hash to authenticate in all communication with the backend API, including login, registration and changing of passwords. This allows an attacker in possession of a hash to takeover a user's account, rendering the benefits of storing hashed passwords in the database useless.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2021-36460?

It affects 1 product.


Products: Veryfitpro Project Veryfitpro.

## How do I fix CVE-2021-36460?

No fix has been published for CVE-2021-36460 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-36460 being exploited?

There is no known exploitation of CVE-2021-36460 in the wild and no public exploit code.

Public exploit code:

- https://github.com/martinfrancois/CVE-2021-36460 (github_poc): https://github.com/martinfrancois/CVE-2021-36460

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-36460 and fix it if it is affected.

What it is: CVE-2021-36460 is a high-severity authentication bypass vulnerability in n/a, published on 25 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-36460 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-36460/ (Markdown: https://insights.sbomify.com/CVE-2021-36460/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-36460
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-36460
- OSV: https://osv.dev/vulnerability/CVE-2021-36460

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-36460/
Summaries are generated and may contain mistakes; the official description above is the record.