CVE-2025-15541VulnerabilityPublished 29 Jan 2026

CVE-2025-15541: TP-Link Systems VX800v v1.0 · Link Following

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

Not known to be exploited · CVSS 6.9 Medium : upgrade to 800.0.11 (0.11.0 3.0.0 v603c.0 Build 250702) when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 800.0.11 (0.11.0 3.0.0 v603c.0 Build 250702)

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

Attack Vector: Adjacent
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: Low
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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to 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-26.

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.11 (0.11.0 3.0.0 v603c.0 Build 250702).

Affected software

Product	Affected	Fixed in
TP-Link Systems Inc.VX800v v1.0	Affected =0	Fixed in 800.0.11 (0.11.0 3.0.0 v603c.0 Build 250702)

AI-suggested

1. Restrict SFTP service access on VX800v devices to trusted administrators and secure network segments, minimizing the number of users with authenticated access. 2. Implement network segmentation and strict access controls to limit adjacency exposure, ensuring that only authorized devices and users can reach the SFTP service. 3. Monitor SFTP logs and system file access patterns for unusual symbolic link usage or access to sensitive files outside expected directories. 4. Employ host-based intrusion detection systems (HIDS) to detect anomalous file access behaviors on VX800v devices. 5. Coordinate with TP-Link for timely security patches or firmware updates addressing this vulnerability and apply them promptly once available. 6. Consider temporary compensating controls such as disabling the SFTP service if not essential or replacing it with more secure file transfer mechanisms. 7. Conduct regular security audits and penetration tests focusing on symbolic link handling and file access controls within network devices. 8. Educate network administrators about the risks of symbolic link vulnerabilities and the importance of strict privilege management.

Description

Improper link resolution in the VX800v v1.0 SFTP service allows authenticated adjacent attackers to use crafted symbolic links to access system files, resulting in high confidentiality impact and limited integrity risk.

Impact

For European organizations, the primary impact of CVE-2025-15541 is the potential unauthorized disclosure of sensitive system files on TP-Link VX800v devices. This can include configuration files, credentials, or other critical data stored on the device, which could facilitate further attacks or data breaches. Organizations in sectors such as telecommunications, critical infrastructure, and enterprise networks that deploy VX800v devices for network management or communication services are at particular risk. The confidentiality breach could lead to exposure of internal network details or security configurations, undermining trust and compliance with data protection regulations like GDPR. The limited integrity risk means attackers are less likely to alter system files directly, but the information gained could enable subsequent attacks. Since exploitation requires authenticated access and network adjacency, the threat is more relevant to insider threats or attackers who have already compromised part of the network. The absence of known exploits reduces immediate risk but also means organizations should proactively address the vulnerability to prevent future exploitation.

CWE-59Improper Link Resolution Before File Access ('Link Following') (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
Architecture and Design · Separation of Privilege
Follow the principle of least privilege when assigning access rights to entities in a software system.
OWASP Cheat Sheets
Authorization (opens in a new tab)
Attack patterns
Symlink Attack (opens in a new tab)
Using Malicious Files (opens in a new tab)
Leverage Executable Code in Non-Executable Files (opens in a new tab)
Manipulating Web Input to File System Calls (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 29 Jan 2026, 18:43 UTC

WeaknessesCWE-59

Technical details

References

Community reviews

Related threats