CVE-2025-13399
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe VX800v v1.0 web interface implements application layer encryption using a weak AES key that can be brute forced by an adjacent attacker. An attacker with network proximity can intercept encrypted traffic and recover the weak key, enabling decryption of sensitive data in transit.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 800.0.11CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLocate the device label or check the admin interface for the exact model number. Confirm it is a TP-Link VX800v.Affected if The device model is TP-Link VX800v
-
Check the installed firmware versionAccess the router admin panel, navigate to the System or Status section, and record the firmware version number. Compare it to the affected range.Affected if Firmware version is below 800.0.11
-
Confirm the web interface is enabledCheck the router settings to verify that the web-based management interface is currently active and accessible.Affected if The web interface is enabled and accessible on the local network
-
Assess network exposureReview the network configuration to determine if the device management interface is reachable from untrusted network segments. Check if the web interface binds to WAN or is accessible beyond the local LAN.Affected if The web interface is exposed to an adjacent or untrusted network segment
The environment is affected if it uses a TP-Link VX800v device with firmware version below 800.0.11 and has the web interface enabled and accessible from an adjacent network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped800.0.11
Contact the vendor for a firmware/security update that implements a cryptographically strong AES key. If no update is available, consider network segmentation to limit adjacent attack surface and disable the web interface if not essential.
Vx800v Firmware 800.0.11
- Download firmware version 800.0.11 or later from the official TP-Link support website for the VX800v model
- Access the VX800v router's web management interface through a browser on a trusted network
- Navigate to the System or Administration settings menu
- Locate the Firmware Upgrade or Update section
- Upload the downloaded firmware file and initiate the upgrade process
- Wait for the upgrade to complete and the device to reboot automatically
- Verify the firmware version has been updated to 800.0.11 or later in the system information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13399 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13399 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data