# CVE-2025-13293: Backdoor / default root credentials

> An unauthenticated remote attacker can gain root access to TBEA TLogger devices via SSH using hard-coded default credentials, leading to full administrative control.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-8hj2-2q8g-jqhw

## What is CVE-2025-13293?

CVE-2025-13293 is a critical vulnerability in TBEA TLogger (TBEA Communication Box 3rd Generation), published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A hard-coded or default root account credential in TBEA TLogger V2.1.0.0B0.0.0.0 allows an unauthenticated remote attacker to obtain root-level access to the device via the exposed SSH service. The root password can be recovered from the password hash stored in /etc/shadow and used to authenticate to the SSH service. Successful exploitation provides full administrative control of the affected device.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2025-13293 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13293 is a critical vulnerability in TBEA TLogger (TBEA Communication Box 3rd Generation), published on 10 Aug 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-13293 in the wild and no public exploit code.

Affected product: TBEA TLogger (TBEA Communication Box 3rd Generation). 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-13293/ (Markdown: https://insights.sbomify.com/CVE-2025-13293/index.md)
```

## Sources

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

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