{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-15543 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-15543 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-15543 is a medium-severity path traversal vulnerability in TP-Link Systems Inc. VX800v v1.0, published on 29 Jan 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-15543 and fix it if it is affected.\n\nWhat it is: CVE-2025-15543 is a medium-severity path traversal vulnerability in TP-Link Systems Inc. VX800v v1.0, published on 29 Jan 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-15543 in the wild and no public exploit code.\n\nAffected product: TP-Link Systems Inc. VX800v 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-15543/ (Markdown: https://insights.sbomify.com/CVE-2025-15543/index.md)","id":"CVE-2025-15543","markdown":"https://insights.sbomify.com/CVE-2025-15543/index.md","name":"CVE-2025-15543","record":{"aliases":["GHSA-45cj-cpr6-w4fh"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TP-Link VX800v","requires_auth":"none","summary":"An attacker with physical access can use a crafted USB device to read root filesystem contents via improper link resolution in the USB HTTP access path.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[{"product":"vx800v_firmware","vendor":"tp-link"}],"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":"Improper link resolution in USB HTTP access path in VX800v v1.0 allows a crafted USB device to expose root filesystem contents, giving an attacker with physical access read‑only access to system files.","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":"Read-Only Root Access via USB Storage Device in TP-Link VX800v","id":"CVE-2025-15543","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Weak Credential Protection During TP-Link Omada Device Adoption","id":"CVE-2025-15544"},"packages":[],"prev":{"headline":"Denial of Service (DoS) of VoIP Communication on TP-Link VX800v","id":"CVE-2025-15542"},"products":["VX800v v1.0"],"published":"2026-01-29","related":[{"cvss_score":7.7,"headline":"Insecure Encryption in Communication with the Web Interface on TP-Link VX800v","id":"CVE-2025-13399","kev_date_added":null,"published":"2026-01-29"},{"cvss_score":6.9,"headline":"Access to System Files via SFTP on TP-Link VX800v","id":"CVE-2025-15541","kev_date_added":null,"published":"2026-01-29"},{"cvss_score":6.3,"headline":"Denial of Service (DoS) of VoIP Communication on TP-Link VX800v","id":"CVE-2025-15542","kev_date_added":null,"published":"2026-01-29"},{"cvss_score":5.3,"headline":"Missing Application-Layer Encryption in Web Interface Endpoints on TP-Link VX800v","id":"CVE-2025-15548","kev_date_added":null,"published":"2026-01-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-01-29","vendors":["TP-Link Systems Inc."]},"summary":"An attacker with physical access can use a crafted USB device to read root filesystem contents via improper link resolution in the USB HTTP access path.","url":"https://insights.sbomify.com/CVE-2025-15543/"}