# CVE-2025-61234: Missing authorization in n/a

> An unauthenticated attacker on the local network can access the Dataphone A920 service on port 8888, exposing device functionality and build information.

- **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:** 29 Oct 2025
- **Updated:** 30 Oct 2025
- **Also known as:** GHSA-g7mp-3c2c-6235

## What is CVE-2025-61234?

CVE-2025-61234 is a high-severity missing authorization vulnerability in n/a, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect access control on Dataphone A920 v2025.07.161103 exposes a service on port 8888 by default on the local network without authentication. This allows an attacker to interact with the device via a TCP socket without credentials. Additionally, sending an HTTP request to the service on port 8888 triggers an error in the response, which exposes the functionality, headers identifying Paytef dataphone packets, and the build version.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-61234 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61234 is a high-severity missing authorization vulnerability in n/a, published on 29 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-61234 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-61234/ (Markdown: https://insights.sbomify.com/CVE-2025-61234/index.md)
```

## Sources

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

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