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

> Attackers can brute force user tokens due to weak validation, allowing unauthorized access to other users' private data.

- **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-cv6r-2w34-jh66

## What is CVE-2025-61114?

CVE-2025-61114 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

2nd Line Android App version v1.2.92 and before (package name com.mysecondline.app), developed by AutoBizLine, Inc., contains an improper access control vulnerability in its authentication mechanism. The server only validates the first character of the user_token, enabling attackers to brute force tokens and perform unauthorized queries on other user accounts. Successful exploitation could result in privacy breaches and unauthorized access to user data.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-61114 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61114 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61114 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61114 exists.

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-61114/ (Markdown: https://insights.sbomify.com/CVE-2025-61114/index.md)
```

## Sources

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

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