CVE-2025-15543VulnerabilityPublished 29 Jan 2026

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

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

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

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score

5.1Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% 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:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Physical
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
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: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable system. Physical interaction may be brief (e.g., evil maid attack) or persistent.
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: 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: 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 26 Oct 2026.

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 physical access to TP-Link VX800v devices to authorized personnel only, employing locked cabinets or secure rooms. 2. Implement strict USB device control policies, including disabling unused USB ports or using endpoint security solutions that monitor and block unauthorized USB devices. 3. Regularly audit and monitor device logs for unusual USB connection events or access patterns. 4. Coordinate with TP-Link for timely updates and patches addressing this vulnerability; apply patches immediately upon release. 5. Consider network segmentation to isolate VX800v devices from critical infrastructure to limit lateral movement if compromise occurs. 6. Conduct security awareness training emphasizing the risks of physical device tampering. 7. Evaluate alternative hardware or firmware versions if available that are not affected by this vulnerability.

Description

Improper link resolution in USB HTTP access path in VX800v v1.0 allows a crafted USB device to expose root filesystem contents, giving an attacker with physical access read‑only access to system files.

Impact

For European organizations, the primary impact of CVE-2025-15543 is the potential unauthorized disclosure of sensitive system files on TP-Link VX800v devices. This could include configuration files, credentials, or other critical data that attackers could use to further compromise the device or network. Although the vulnerability only allows read-only access and requires physical access, environments with shared or poorly controlled physical access (e.g., data centers, offices, or public areas) are at risk. Exposure of root filesystem contents could facilitate subsequent attacks or insider threats. The impact on confidentiality is high, while integrity and availability remain unaffected. Organizations relying on VX800v devices for network infrastructure or security functions may face operational risks if attackers leverage disclosed information. The medium severity rating reflects the balance between the physical access requirement and the sensitivity of exposed data.

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:42 UTC

WeaknessesCWE-59

Technical details

References

Community reviews

Related threats