CVE-2025-15548VulnerabilityPublished 29 Jan 2026Updated 13 Feb 2026

CVE-2025-15548: TP-Link Systems VX800v v1.0 · Missing Encryption of Sensitive Data

Affects TP-Link Systems VX800v v1.0Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 800.0.18_0.18.0 3.0.0 v603c.0 Build 260203 Rel.35251n when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 800.0.18_0.18.0 3.0.0 v603c.0 Build 260203 Rel.35251n

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Adjacent
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable system is bound to a protocol stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared proximity (e.g., Bluetooth, NFC, or IEEE 802.11) or logical network (e.g., local IP subnet), or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN within an administrative network zone).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade TP-Link Systems VX800v v1.0 to 800.0.18_0.18.0 3.0.0 v603c.0 Build 260203 Rel.35251n.

Affected software

Product	Affected	Fixed in
TP-Link Systems Inc.VX800v v1.0	Affected =0	Fixed in 800.0.18_0.18.0 3.0.0 v603c.0 Build 260203 Rel.35251n

AI-suggested

1. Immediately segment networks to isolate VX800v devices from untrusted or public network segments, restricting access to trusted administrators only. 2. Disable or restrict access to the vulnerable web interface endpoints transmitting data over HTTP, if possible, or disable the web management interface entirely if not required. 3. Use VPNs or secure tunnels to access device management interfaces, ensuring encryption at the transport layer. 4. Monitor network traffic for unencrypted HTTP communications involving VX800v devices and investigate any suspicious activity. 5. Implement strict network access controls and 802.1X authentication to limit network adjacency exposure. 6. 7. Educate network administrators about the risks of unencrypted management interfaces and enforce strong password policies to reduce the impact if credentials are intercepted. 8. Consider replacing VX800v devices with models that support encrypted management protocols if feasible.

Description

Some VX800v v1.0 web interface endpoints transmit sensitive information over unencrypted HTTP due to missing application layer encryption, allowing a network adjacent attacker to intercept this traffic and compromise its confidentiality.

Impact

For European organizations, the primary impact of CVE-2025-15548 is the potential compromise of sensitive information transmitted between users and TP-Link VX800v devices. This could include administrative credentials, configuration details, or session tokens, which if intercepted, may allow attackers to gain unauthorized access or control over the device. Such access could lead to network reconnaissance, lateral movement, or disruption of services. Organizations with VX800v devices deployed in critical infrastructure, enterprise networks, or sensitive environments face increased risk. The vulnerability is particularly concerning in environments with shared or untrusted networks, such as corporate Wi-Fi, public access points, or multi-tenant facilities common in European urban centers. Although the vulnerability does not directly impact system integrity or availability, the confidentiality breach could be a stepping stone for more severe attacks. The absence of patches increases exposure duration, necessitating compensating controls. Overall, the impact is moderate but significant for organizations relying on these devices for network management or connectivity.

CWE-311Missing Encryption of Sensitive Data (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not encrypt sensitive or critical information before storage or transmission.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements
Clearly specify which data or resources are valuable enough that they should be protected by encryption. Require that any transmission or storage of this data/resource should use well-vetted encryption algorithms.
Architecture and Design
Ensure that encryption is properly integrated into the system design, including but not necessarily limited to: Encryption that is needed to store or transmit private data of the users of the system; Encryption that is needed to protect the system itself from unauthorized disclosure or tampering
Architecture and Design · Libraries or Frameworks
When there is a need to store or transmit sensitive data, use strong, up-to-date cryptographic algorithms to encrypt that data. Select a well-vetted algorithm that is currently considered to be strong by experts in the field, and use well-tested implementations.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
User Privacy Protection (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V6.1.3 (opens in a new tab)
V6.1.2 (opens in a new tab)
V6.1.1 (opens in a new tab)
Attack patterns
Sniffing Attacks (opens in a new tab)
Sniffing Network Traffic (opens in a new tab)
Lifting Sensitive Data Embedded in Cache (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Feb 2026, 11:19 UTC

WeaknessesCWE-311

Technical details

References

Community reviews

Related threats