HB810(US2) V1.0/1.6/2.0/2.6 vulnerability

What happened

The affected TP-Link Aginet devices contain a flaw in the web management interface where authentication checks are not consistently enforced on certain endpoints. An attacker can send specially crafted requests to bypass authentication and directly invoke privileged functionality without valid credentials. This issue arises from improper enforcement of access control mechanisms on sensitive operations. Successful exploitation may allow an unauthenticated attacker to execute privileged operations and gain full control of the device.

Affected versions

HB810(US2) V1.0/1.6/2.0/2.6: before 0.9.0 3.2.2 v6095.0 Build 260717 Rel.67188n (custom); before 0.10.0 3.2.2 v6095.0 Build 260306 Rel.47567n (custom); before 0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n (custom); before 0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n (custom); before 0.6.0 3.0.0 v60af.0 Build 251216 Rel.46954n (custom); before 0.3.0 3.0.0 v60bf.0 Build 250901 Rel.45574n (custom); before 0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n (custom); before 0.5.0 3.0.0 v60d5.0 Build 250922 Rel.13742n (custom); before 0.8.0 3.0.0 v60d5.0 Build 260318 Rel.78363n (custom); before 0.14.0 3.0.0 v6065.0 Build 250822 Rel.81150n (custom); before 0.17.0 3.2.2 v6065.0 Build 260722 Rel.10662n (custom); before 0.5.0 3.1.10 v6075.0 Build 260511 Rel.47847n (custom); before 0.4.0 3.1.10 v6082.0 Build 260204 Rel.49460n (custom); before 0.18.0 2.0.0 v605f.0 Build 260304 Rel.45905n (custom); before 0.21.0 2.0.0 v605f.0 Build 250306 Rel.9224n (custom); before 1.2.0 3.1.0 v609d.0 Build 260128 Rel.29711n (custom); before 0.18.0 2.0.0 v605e.0 Build 250827 Rel.37904n (custom); before 0.17.0 2.0.0 v605e.0 Build 250618 Rel.19329n (custom); before 1.8.0 3.1.0 v608a.0 Build 250425 Rel.40905n (custom); before 1.7.0 3.1.0 v608a.0 Build 250418 Rel.8257n (custom); before 0.20.0 2.0.0 v605f.0 Build 250305 Rel.14728n (custom); before 0.19.0 2.0.0 v609b.0 Build 250814 Rel.49732n (custom); before 0.20.0 2.0.0 v609b.0 Build 260427 Rel.16915 (custom); before 0.9.0 3.0.0 v607e.0 Build 260520 Rel.33425n (custom); before 0.8.0 3.0.0 v607e.0 Build 260424 Rel.27419n (custom); before 0.7.0 3.0.0 v60b4.0 Build 251229 Rel.84306n (custom); before 0.1.0 3.0.0 v60ee.0 Build 250310 Rel.55637n (custom); before 0.3.0 3.0.0 v60e3.0 Build 250925 Rel.66797n (custom); before 0.4.0 3.1.9 v6087.0 Build 250928 Rel.59674n (custom); before 0.8.0 3.2.2 v6080.0 Build 260309 Rel.54790n (custom); before 1.16.0 0.8.0 v6062.0 Build 250817 Rel.23310n (custom); before 0.6.0 3.0.0 v6096.0 Build 250416 Rel.26048n (custom); before 0.4.0 3.1.10 v60dc.0 Build 250520 Rel.69748n (custom); before 0.3.0 3.1.10 v6107.0 Build 250425 Rel.71973n (custom); before 0.16.0 3.0.0 v6066.0 Build 250423 Rel.43799n (custom); before 800.0.16 (custom); before 0.14.0 2.0.0 v6092.0 Build 250417 Rel.24761n (custom); before 0.2.0 2.0.0 v60df.0 Build 250427 Rel.38233n (custom) Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

• Apply vendor-provided updates or mitigations.
• Review affected product exposure and access logs.