What is CVE-2025-30240?
The affected TP-Link Aginet devices do not properly validate symbolic links created on external USB storage devices. By placing a crafted symbolic link on supported storage media, an attacker may cause the system to resolve the link. Successful exploitation may allow unauthorized read access to sensitive files within the device filesystem.
The record classifies CVE-2025-30240 under weakness class CWE-59. 12 affected-product entries are recorded, across 1 vendor, listed below. The identifier was first published 56 days ago.
Severity and exploitation probability
- CVSS v4.0 base score
- 5.1 — Medium (derived from score)
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 - EPSS (FIRST)
- 0.1% probability of exploitation in the next 30 days, higher than 7.0% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 2.8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-08-10
Is CVE-2025-30240 being exploited?
It currently carries a trending score of 31 in the Threadlinqs vulnerability feed.
Affected products and versions
- TP-Link Systems Inc.: HB810(US2) V1.0/1.6/2.0/2.6, HB810(EU1) V2.0, HB710(US2) V1.6/1.0, HB710(EU1) 1.0, HB610(US2) V2.6/2.0, HB610(EU1), HB610(CA) V2.0, HB410( EU1) 1.0, HB210(US2) 1.0, HB210(EU1) 1.0, HB210 Pro(EU1)1.0, HB210 Pro(US2)1.0/1.6
How to fix CVE-2025-30240
No vendor patch reference has been recorded for CVE-2025-30240 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2025-30240
No threat campaign in the Threadlinqs corpus currently references CVE-2025-30240, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, NVD, FIRST EPSS. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.