# CVE-2025-13315: Unauthenticated log access in Twonky Server

> Unauthenticated attackers can bypass API authentication to access log files, exposing administrator credentials in Twonky Server.

- **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:** 19 Nov 2025
- **Updated:** 19 Nov 2025
- **Also known as:** GHSA-x96r-v3vc-578h

## What is CVE-2025-13315?

CVE-2025-13315 is a critical vulnerability in Lynxtechnology Twonky Server, published on 19 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Twonky Server 8.5.2 on Linux and Windows is vulnerable to an access control flaw. An unauthenticated attacker can bypass web service API authentication controls to leak a log file and read the administrator's username and encrypted password.

Weakness: CWE-420 (Unprotected Alternate Channel)

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

It affects 1 product.


Products: Lynxtechnology Twonky Server.

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

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

## Is CVE-2025-13315 being exploited?

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

Public exploit code:

- CVE-2025-13315 (github_poc): https://github.com/0xredash/CVE-2025-13315
- Twonky Server Log Leak Authentication Bypass (metasploit)
- Twonky Server 8.5.2 on Linux and Windows - Log File Exposure (nuclei): http/cves/2025/CVE-2025-13315.yaml

## Other vulnerabilities in Lynxtechnology Twonky Server

- [CVE-2025-13316](https://insights.sbomify.com/CVE-2025-13316/): Hard-coded encryption keys in Twonky Server (high 8.2)
- [CVE-2018-7171](https://insights.sbomify.com/CVE-2018-7171/): Path traversal in n/a (high 7.5)
- [CVE-2018-9177](https://insights.sbomify.com/CVE-2018-9177/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2018-9182](https://insights.sbomify.com/CVE-2018-9182/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2018-7203](https://insights.sbomify.com/CVE-2018-7203/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13315 is a critical vulnerability in Lynxtechnology Twonky Server, published on 19 Nov 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-13315 exists.

Affected product: Lynxtechnology Twonky Server. 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-13315/ (Markdown: https://insights.sbomify.com/CVE-2025-13315/index.md)
```

## Sources

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

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