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

> Attackers can bypass authentication and access premium features by tampering with local storage parameters in the mobile application.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qm7m-g6p5-jmmr

## What is CVE-2021-25648?

CVE-2021-25648 is a critical authentication bypass vulnerability in n/a, published on 16 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mobile application "Testes de Codigo" 11.4 and prior allows an attacker to gain access to the administrative interface and premium features by tampering the boolean value of parameters "isAdmin" and "isPremium" located on device storage.

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

It affects 1 product.


Products: Testes-Codigo Testes De Codigo.

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

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

## Is CVE-2021-25648 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-25647](https://insights.sbomify.com/CVE-2021-25647/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-25648 is a critical authentication bypass vulnerability in n/a, published on 16 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-25648 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-25648/ (Markdown: https://insights.sbomify.com/CVE-2021-25648/index.md)
```

## Sources

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

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