CyberSecBulletin
CVE-2025-30237NVD status: Awaiting Analysis

HB810(US2) V1.0/1.6/2.0/2.6: Missing Authorization

Published Updated By the CyberSecBulletin desk

CVE-2025-30237 is a high-severity missing authorization vulnerability in HB810(US2) V1.0/1.6/2.0/2.6 from TP-Link, with a CVSS 4.0 base score of 8.7 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists version 0.9.0 3.2.2 v6095.0 Build 260717 Rel.67188n as the first without the flaw, so updating HB810(US2) V1.0/1.6/2.0/2.6 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.33% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update HB810(US2) V1.0/1.6/2.0/2.6 to 0.9.0 3.2.2 v6095.0 Build 260717 Rel.67188n or a later version.
  2. Update HB810(EU1) V2.0 to 0.10.0 3.2.2 v6095.0 Build 260306 Rel.47567n or a later version.
  3. Update HB710(US2) V1.6/1.0 to 0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
TP-LinkHB810(US2) V1.0/1.6/2.0/2.6before 0.9.0 3.2.2 v6095.0 Build 260717 Rel.67188n0.9.0 3.2.2 v6095.0 Build 260717 Rel.67188n
TP-LinkHB810(EU1) V2.0before 0.10.0 3.2.2 v6095.0 Build 260306 Rel.47567n0.10.0 3.2.2 v6095.0 Build 260306 Rel.47567n
TP-LinkHB710(US2) V1.6/1.0before 0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n
TP-LinkHB710(EU1) 1.0before 0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n0.3.0 3.0.0 v60be.0 Build 251128 Rel.43956n
TP-LinkHB610(US2) V2.6/2.0before 0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n
TP-LinkHB610(EU1)before 0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n0.6.0 3.0.0 v60af.0 Build 251204 Rel.20362n
TP-LinkHB610(CA) V2.0before 0.6.0 3.0.0 v60af.0 Build 251216 Rel.46954n0.6.0 3.0.0 v60af.0 Build 251216 Rel.46954n
TP-LinkHB410( EU1) 1.0before 0.3.0 3.0.0 v60bf.0 Build 250901 Rel.45574n0.3.0 3.0.0 v60bf.0 Build 250901 Rel.45574n
TP-LinkHB210(US2) 1.0before 0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n
TP-LinkHB210(EU1) 1.0before 0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n0.2.0 3.0.0 v60f9.0 Build 250826 Rel.47715n
TP-LinkHB210 Pro(EU1)1.0before 0.5.0 3.0.0 v60d5.0 Build 250922 Rel.13742n0.5.0 3.0.0 v60d5.0 Build 250922 Rel.13742n
TP-LinkHB210 Pro(US2)1.0/1.6before 0.8.0 3.0.0 v60d5.0 Build 260318 Rel.78363n0.8.0 3.0.0 v60d5.0 Build 260318 Rel.78363n
TP-LinkHX510(US1) V2.0before 0.14.0 3.0.0 v6065.0 Build 250822 Rel.81150n0.14.0 3.0.0 v6065.0 Build 250822 Rel.81150n
TP-LinkHX510(EU1) V2.0before 0.14.0 3.0.0 v6065.0 Build 250822 Rel.81150n0.14.0 3.0.0 v6065.0 Build 250822 Rel.81150n
TP-LinkHX510(CA) V1.0/2.0before 0.14.0 3.0.0 v6065.0 Build 250822 Rel.81150n0.14.0 3.0.0 v6065.0 Build 250822 Rel.81150n
TP-LinkHX510(AU) V1.0/2.0before 0.14.0 3.0.0 v6065.0 Build 250822 Rel.81150n0.14.0 3.0.0 v6065.0 Build 250822 Rel.81150n
TP-LinkHX510(US2) 2.6before 0.17.0 3.2.2 v6065.0 Build 260722 Rel.10662n0.17.0 3.2.2 v6065.0 Build 260722 Rel.10662n
TP-LinkHX710(EU1) V1.0before 0.5.0 3.1.10 v6075.0 Build 260511 Rel.47847n0.5.0 3.1.10 v6075.0 Build 260511 Rel.47847n
TP-LinkHX710 Pro(EU1) V1.0before 0.4.0 3.1.10 v6082.0 Build 260204 Rel.49460n0.4.0 3.1.10 v6082.0 Build 260204 Rel.49460n
TP-LinkHX220(US1) V1.0/1.6before 0.18.0 2.0.0 v605f.0 Build 260304 Rel.45905n0.18.0 2.0.0 v605f.0 Build 260304 Rel.45905n
TP-LinkHX220(EU1) V1.0before 0.18.0 2.0.0 v605f.0 Build 260304 Rel.45905n0.18.0 2.0.0 v605f.0 Build 260304 Rel.45905n
TP-LinkHX220(CA) V1.0before 0.21.0 2.0.0 v605f.0 Build 250306 Rel.9224n0.21.0 2.0.0 v605f.0 Build 250306 Rel.9224n
TP-LinkHX220(AU) V1.0before 0.21.0 2.0.0 v605f.0 Build 250306 Rel.9224n0.21.0 2.0.0 v605f.0 Build 250306 Rel.9224n
TP-LinkHX141(EU1) V1.0before 1.2.0 3.1.0 v609d.0 Build 260128 Rel.29711n1.2.0 3.1.0 v609d.0 Build 260128 Rel.29711n
TP-LinkHC220-G5(US1) V1.0/1.6before 0.18.0 2.0.0 v605e.0 Build 250827 Rel.37904n0.18.0 2.0.0 v605e.0 Build 250827 Rel.37904n

Version data comes from the organisation that assigned the CVE; 31 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Attack requirements
NoneThe attack does not depend on a particular deployment or configuration.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Confidentiality (vulnerable system)
HighSerious loss of confidentiality on the vulnerable system.
Integrity (vulnerable system)
HighSerious loss of integrity on the vulnerable system.
Availability (vulnerable system)
HighSerious loss of availability on the vulnerable system.
Confidentiality (other systems)
NoneNo loss of confidentiality on systems beyond the vulnerable one.
Integrity (other systems)
NoneNo loss of integrity on systems beyond the vulnerable one.
Availability (other systems)
NoneNo loss of availability on systems beyond the vulnerable one.

Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. Scored by CNA.

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

How developers prevent this class of flaw

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.

More Missing Authorization vulnerabilities (CWE-862)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in HB810(US2) V1.0/1.6/2.0/2.6

All HB810(US2) V1.0/1.6/2.0/2.6 vulnerabilities

Recent Missing Authorization vulnerabilities

Spotted an error? Tell us.