# CVE-2025-15385: Auth bypass in com.afmobi.boomplayer

> An attacker can bypass authentication in the TECNO Boomplayer mobile application due to insufficient data authenticity verification.

- **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:** 6 Jan 2026
- **Updated:** 6 Jan 2026
- **Also known as:** GHSA-w2qf-83rm-prj9

## What is CVE-2025-15385?

CVE-2025-15385 is a critical authentication bypass vulnerability in TECNO Mobile com.afmobi.boomplayer, published on 6 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insufficient Verification of Data Authenticity vulnerability in TECNO Mobile com.Afmobi.Boomplayer allows Authentication Bypass.This issue affects com.Afmobi.Boomplayer: 7.4.63.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 1 product.


Products: Tecno Boomplay.

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

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

## Is CVE-2025-15385 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15385 is a critical authentication bypass vulnerability in TECNO Mobile com.afmobi.boomplayer, published on 6 Jan 2026. 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-15385 in the wild and no public exploit code.

Affected product: TECNO Mobile com.afmobi.boomplayer. 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-15385/ (Markdown: https://insights.sbomify.com/CVE-2025-15385/index.md)
```

## Sources

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

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