# CVE-2025-13399: Insecure Encryption in Communication with the Web Interface on TP-Link VX800v

> An adjacent attacker can brute force weak AES keys to decrypt, modify, or disrupt traffic on the TP-Link VX800v web interface.

- **Severity:** High 7.7 (`CVSS:4.0/AV:A/AC:H/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-8cjc-9g75-5fr7

## What is CVE-2025-13399?

CVE-2025-13399 is a high-severity vulnerability in TP-Link Systems Inc. VX800v v1.0, published on 29 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A weakness in the web interface’s application layer encryption in VX800v v1.0 allows an adjacent attacker to brute force the weak AES key and decrypt intercepted traffic. Successful exploitation requires network proximity but no authentication, and may result in high impact to confidentiality, integrity, and availability of transmitted data.

Weakness: CWE-331 (Insufficient Entropy)

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

It affects 1 product.


Products: Tp-Link Vx800v Firmware.

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

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

## Is CVE-2025-13399 being exploited?

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

## Other vulnerabilities in TP-Link Systems Inc. VX800v v1.0

- [CVE-2025-15541](https://insights.sbomify.com/CVE-2025-15541/): Access to System Files via SFTP on TP-Link VX800v (medium 6.9)
- [CVE-2025-15542](https://insights.sbomify.com/CVE-2025-15542/): Denial of Service (DoS) of VoIP Communication on TP-Link VX800v (medium 6.3)
- [CVE-2025-15548](https://insights.sbomify.com/CVE-2025-15548/): Missing Application-Layer Encryption in Web Interface Endpoints on TP-Link VX800v (medium 5.3)
- [CVE-2025-15543](https://insights.sbomify.com/CVE-2025-15543/): Read-Only Root Access via USB Storage Device in TP-Link VX800v (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13399 is a high-severity vulnerability in TP-Link Systems Inc. VX800v v1.0, published on 29 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13399 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. VX800v v1.0. 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-13399/ (Markdown: https://insights.sbomify.com/CVE-2025-13399/index.md)
```

## Sources

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

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