{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-30240 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-30240 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-30240 is a medium-severity path traversal vulnerability in TP-Link Systems Inc. EB810v(EU1) V1.0, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-30240 and fix it if it is affected.\n\nWhat it is: CVE-2025-30240 is a medium-severity path traversal vulnerability in TP-Link Systems Inc. EB810v(EU1) V1.0, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-30240 in the wild and no public exploit code.\n\nAffected product: TP-Link Systems Inc. EB810v(EU1) V1.0. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-30240/ (Markdown: https://insights.sbomify.com/CVE-2025-30240/index.md)","id":"CVE-2025-30240","markdown":"https://insights.sbomify.com/CVE-2025-30240/index.md","name":"CVE-2025-30240","record":{"aliases":["GHSA-8vgw-m5fh-hwg3"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TP-Link Aginet router","requires_auth":"none","summary":"Attackers can read sensitive files on TP-Link Aginet devices by exploiting improper symlink handling on USB storage.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"The affected TP-Link Aginet devices do not properly validate symbolic links created on external USB storage\ndevices. By placing a crafted symbolic link on supported storage media, an\nattacker may cause the system to resolve the link.\n\nSuccessful\nexploitation may allow unauthorized read access to sensitive files within the\ndevice filesystem.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Arbitrary File Read via Improper Symlink Handling in USB HTTPS Access Path in multiple TP-Link Aginet Devices","id":"CVE-2025-30240","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"OS Command Injection in Web Interface in Multiple TP-Link Aginet Devices","id":"CVE-2025-30241"},"packages":[],"prev":{"headline":"Sensitive Data Exposure due to Hardcoded Cryptographic Keys in Multiple TP-Link Aginet Devices","id":"CVE-2025-30239"},"products":["EB810v(EU1) V1.0","EX220(BR) V1.0/1.20/1.28/1.29/1.8","EX220(BR) V2.0","EX220(EU1) V1.0/1.20","EX220(RU) V1.0","EX220(US1) V1.0","EX222(EU1) V1.0","EX222(KR) V1.0","EX222(US1) V1.0","EX520v(EU1)1.0","EX820v(EU1) V1.0","EX920(US2) V1.6/V1.0","HB210 Pro(EU1)1.0","HB210 Pro(US2)1.0/1.6","HB210(EU1) 1.0","HB210(US2) 1.0","HB410( EU1) 1.0","HB610(CA) V2.0","HB610(EU1)","HB610(US2) V2.6/2.0","HB710(EU1) 1.0","HB710(US2) V1.6/1.0","HB810(EU1) V2.0","HB810(US2) V1.0/1.6/2.0/2.6","VX1800v(EU1) V1.0","VX420-G2h(AU) V3.0","VX800v(DE) V1.0","XC220-G3v(EU1) V2.30","XC220-G3v(US1) V2.30","XX530v(BR)v1.0","XX530v(BR)v2.0","XX530v(EU1)","XX530v(US1)"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-12","vendors":["TP-Link Systems Inc."]},"summary":"Attackers can read sensitive files on TP-Link Aginet devices by exploiting improper symlink handling on USB storage.","url":"https://insights.sbomify.com/CVE-2025-30240/"}