Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Gain adjacent network access (LAN/Wi-Fi)
  2. Delivery
    Authenticate with low-privilege credentials to web UI
  3. Exploit
    Craft payload with shell metacharacters in vulnerable parameter
  4. Install
    Submit HTTP request to vulnerable web interface component
  5. C2
    Trigger unsanitized passthrough to OS command function
  6. Execute
    Execute arbitrary commands with elevated device privileges
  7. Impact
    Full device compromise and persistence

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK

2 techniques across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Two concrete prerequisites must be satisfied. First, the attacker must be on the same adjacent network as the device - connected to the same LAN switch, Wi-Fi SSID, or mesh backhaul network; internet-based remote exploitation is not possible given AV:A in the CVSS 4.0 vector. Second, the attacker must possess at least low-privilege authentication credentials for the device's web management interface (PR:L in CVSS 4.0); unauthenticated exploitation is not supported by the available data. Limiting factors include: the adjacency requirement significantly reduces the potential attacker population to entities already on the local network; low-privilege access is required, meaning stolen or default credentials are a prerequisite rather than optional; and the scope change metrics (SC:N/SI:N/SA:N) indicate that exploitation does not automatically spread to systems beyond the compromised device without additional attacker effort. Non-default or hardened configurations with strong credential policies and network segmentation materially raise the effective exploitation bar.

Impact

The CVSS 4.0 base score of 8.6 with AV:A/PR:L reflects two meaningful constraints: the attacker must already be present on the adjacent network (same LAN or Wi-Fi segment) and must hold at least low-privilege credentials on the device. These factors materially reduce the attack surface compared to an internet-facing, unauthenticated flaw. In a home environment, however, the adjacent-network requirement is often trivially satisfied - any device on the home Wi-Fi qualifies - and default or weak credentials are common on consumer devices, softening the PR:L barrier. No EPSS score was provided in the input data; no KEV listing and no public POC have been identified, indicating the vulnerability has not yet seen widespread active exploitation. The full C:H/I:H/A:H impact reflects that successful exploitation yields full device control, enabling persistent backdoors, traffic interception, lateral movement to adjacent LAN hosts, or use of the device as a pivot point. The primary real-world risk is concentrated in environments where Wi-Fi access is loosely controlled or shared credentials are reused across devices.

Exploit ScenarioDerived

An attacker connected to the same Wi-Fi or LAN segment as an affected TP-Link Aginet device - for example, a malicious guest on a home network, a compromised IoT device, or an insider - authenticates to the device's web management interface using obtained or default credentials. The attacker then submits a crafted HTTP request to a vulnerable web interface component, embedding shell metacharacters (e.g., semicolons, backticks, or pipes) in a parameter that is passed unsanitized to a system command function. The injected command executes with elevated privileges, allowing the attacker to establish a persistent backdoor, exfiltrate Wi-Fi PSKs, or use the device as a network pivot. No public POC has been identified at time of analysis, but the vulnerability class (CWE-78) is well-understood and exploit development is straightforward once the vulnerable endpoint is identified.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 10, 2026

OS command injection in TP-Link Aginet home networking devices (HB, EB, EX, XX, VX series) allows an authenticated attacker on the same network segment to execute arbitrary operating system commands with elevated privileges through unsanitized web interface inputs. The attack vector is adjacent-network only (AV:A per CVSS 4.0), limiting internet-scale exploitation, but a compromised or malicious LAN/Wi-Fi client could fully compromise the affected device. No public exploit code or CISA KEV listing has been identified at time of analysis; TP-Link has released patched firmware across all affected product lines.

RemediationAI

The primary remediation is updating each affected device to its respective patched firmware build as documented in the TP-Link advisory at https://www.tp-link.com/us/support/faq/5239/. Specific fix builds are confirmed by EUVD-2025-210677 and include, for example, HB810(US2) firmware 0.9.0 3.2.2 Build 260717 and VX800v(DE) firmware 800.0.16; consult the advisory for the complete per-model table. Where immediate firmware update is not feasible, restrict access to the device management web interface to trusted hosts only by enabling access control lists or management ACLs if supported by the device. Changing default or weak device credentials reduces the exposure imposed by the PR:L requirement, as an attacker cannot exploit this without valid authentication. Isolating IoT/home networking devices on a dedicated VLAN or network segment limits the blast radius if exploitation occurs - an attacker would be constrained to that segment rather than the full LAN. Disabling remote management (if enabled) provides no direct mitigation since the vector is adjacent-network, not internet-facing, but is still a recommended hardening step. Note that VLAN isolation changes may affect mesh network functionality depending on how backhaul is configured on HB/EX/XX models.

Affected VersionsENISA

HB210 Pro(EU1)1.0 0 <0.5.0 3.0.0 v60d5.0 Build 250922 Rel.13742n
HB610(CA) V2.0 0 <0.6.0 3.0.0 v60af.0 Build 251216 Rel.46954n
HB710(US2) V1.6/1.0 0 <0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n
EX220(RU) V1.0 0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
EX222(US1) V1.0 0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
VX420-G2h(AU) V3.0 0 <0.2.0 2.0.0 v60df.0 Build 250427 Rel.38233n
EX220(BR) V1.0/1.20/1.28/1.29/1.8 0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
HB210(US2) 1.0 0 <0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n
HB610(US2) V2.6/2.0 0 <0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n
EB210 Pro(EU1) 1.0 0 <0.2.0 3.0.0 v60f4.0 Build 250807 Rel.58901n
EB210 Pro(US1) 1.0 0 <0.2.0 3.0.0 v60f4.0 Build 250807 Rel.58901n
HB210 Pro(US2)1.0/1.6 0 <0.8.0 3.0.0 v60d5.0 Build 260318 Rel.78363n
EX520v(EU1)1.0 0 <0.1.0 3.0.0 v60ee.0 Build 250310 Rel.55637n
XX530v(BR)v2.0 0 <0.4.0 3.1.10 v60dc.0 Build 250520 Rel.69748n
EX222(EU1) V1.0 0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
EX820v(EU1) V1.0 0 <0.4.0 3.1.9 v6087.0 Build 250928 Rel.59674n
HB710(EU1) 1.0 0 <0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n
HB810(EU1) V2.0 0 <0.10.0 3.2.2 v6095.0 Build 260306 Rel.47567n
HB410( EU1) 1.0 0 <0.3.0 3.0.0 v60bf.0 Build 250901 Rel.45574n
EB810v(EU1) V1.0 0 <0.6.0 3.0.0 v608b.0 Build 250613 Rel.10497n
EX222(KR) V1.0 0 <0.20.0 2.0.0 v609b.0 Build 260427 Rel.16915
HB610(EU1) 0 <0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n
XX530v(EU1) 0 <0.3.0 3.1.10 v6107.0 Build 250425 Rel.71973n
EX220(EU1) V1.0/1.20 0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
HB810(US2) V1.0/1.6/2.0/2.6 0 <0.9.0 3.2.2 v6095.0 Build 260717 Rel.67188n
VX800v(DE) V1.0 0 <800.0.16
XX230v(BR) V1.0 0 <0.16.0 3.0.0 v6066.0 Build 250423 Rel.43799n
EX920(US2) V1.6/V1.0 0 <0.8.0 3.2.2 v6080.0 Build 260309 Rel.54790n
EX220(US1) V1.0 0 <0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n
EX220(BR) V2.0 0 <0.19.0 2.0.0 v609b.0 Build 250814 Rel.49732n
HB210(EU1) 1.0 0 <0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n

Affected Packages

euvd vx800v_de_v1_0 fix: 800.0.16

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-78 (Improper Neutralization of Special Elements used in an OS Command) describes the root cause: certain web interface handlers pass user-supplied input directly or insufficiently sanitized to system-level functions such as exec(), popen(), or shell wrappers. The affected products span TP-Link's Aginet ecosystem - including HB-series mesh nodes (HB210, HB410, HB610, HB710, HB810), EB-series mesh extenders (EB210 Pro, EB810v), EX-series Wi-Fi range extenders (EX220, EX222, EX520v, EX820v, EX920), XX-series whole-home mesh units (XX230v, XX530v), and VX-series DSL routers (VX420-G2h, VX800v). CPE strings confirm affected hardware SKUs across US, EU, BR, CA, AU, DE, RU, and KR regional variants. The web interface runs with elevated system privileges, so injected commands inherit those privileges without additional escalation steps.

Know when Hb810 Us2 V1 0 1 6 2 0 2 6 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (TPLink) PRIMARY 8.6 HIGH
CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 8.0 HIGH

Adjacent vector and low-privilege authentication required per CVE description and CVSS 4.0 vendor vector; no scope change as device compromise is self-contained.

3.1 AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (TPLink).

CVSS VectorVendor: TPLink

Attack Vector
Adjacent
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Aug 10, 2026 - 23:04 EUVD
CVE Published
Aug 10, 2026 - 22:26 cve.org
HIGH 8.6

DescriptionCVE.org

Certain web interface components in affected TP-Link Aginet devices do not validate and sanitize user-supplied input properly before passing it to system-level command execution functions.  An authenticated adjacent attacker may inject specially crafted input to execute arbitrary operation system commands with elevated privileges.

Successful exploitation may allow execution of arbitrary system commands, potentially leading to full device compromise.

Executive ViewAI

Why It Matters

TP-Link Aginet home networking devices (HB, EB, EX, XX, VX series) are vulnerable to OS command injection through the web interface, allowing authenticated users on the adjacent network to execute arbitrary commands with elevated privileges. This threatens data confidentiality and enables full device compromise, which could serve as a pivot point for lateral network movement in BYOD and enterprise LAN deployments. Patched firmware is available across all affected product lines and should be deployed immediately.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.5%
Top 60% exploitable
Prevalence
Medium
popular consumer mesh and extender line across multiple regions
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

43
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +43
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

OS command injection occurs when an application passes unsanitized user input directly into system shell commands.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy