# CVE-2025-61116: Auth bypass in n/a

> Attackers can bypass authentication in the AdForest Android app by manipulating Base64-encoded email credentials, leading to unauthorized account access and privacy breaches.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Oct 2025
- **Updated:** 30 Oct 2025
- **Also known as:** GHSA-qpc6-vqhv-h5vv

## What is CVE-2025-61116?

CVE-2025-61116 is a high-severity authentication bypass vulnerability in n/a, published on 30 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AdForest - Classified Android App version 4.0.12 (package name scriptsbundle.adforest), developed by Muhammad Jawad Arshad, contains an improper access control vulnerability in its authentication mechanism. The app uses a Base64-encoded email address as the authorization credential, which can be manipulated by attackers to gain unauthorized access to user accounts. Successful exploitation could result in account compromise, privacy breaches, and misuse of the platform.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-61116?


## How do I fix CVE-2025-61116?

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

## Is CVE-2025-61116 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61116 and fix it if it is affected.

What it is: CVE-2025-61116 is a high-severity authentication bypass vulnerability in n/a, published on 30 Oct 2025. 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-2025-61116 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-2025-61116/ (Markdown: https://insights.sbomify.com/CVE-2025-61116/index.md)
```

## Sources

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

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