# CVE-2025-0730: TP-Link TL-SG108E HTTP GET Request usr_account_set.cgi get request method with sensitive query strings

> Attackers can intercept sensitive credentials transmitted via HTTP GET query strings in the web interface, requiring a firmware upgrade to fix.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2025
- **Updated:** 27 Jan 2025
- **Also known as:** GHSA-735v-r5c6-6249

## What is CVE-2025-0730?

CVE-2025-0730 is a medium-severity vulnerability in TP-Link TL-SG108E, published on 27 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability classified as problematic has been found in TP-Link TL-SG108E 1.0.0 Build 20201208 Rel. 40304. Affected is an unknown function of the file /usr_account_set.cgi of the component HTTP GET Request Handler. The manipulation of the argument username/password leads to use of get request method with sensitive query strings. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. Upgrading to version 1.0.0 Build 20250124 Rel. 54920(Beta) is able to address this issue. It is recommended to upgrade the affected component. The vendor was contacted early. They reacted very professional and provided a pre-fix version for their customers.

Weakness: CWE-598 (Use of HTTP Request With Sensitive Query String)

## Which versions are affected by CVE-2025-0730?

It affects 1 product.


Products: Tp-Link Tl-Sg108e Firmware.

## How do I fix CVE-2025-0730?

No fix has been published for CVE-2025-0730 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-0730 being exploited?

There is no known exploitation of CVE-2025-0730 in the wild and no public exploit code.

## Other vulnerabilities in TP-Link TL-SG108E

- [CVE-2017-8074](https://insights.sbomify.com/CVE-2017-8074/): Information disclosure in n/a (critical 9.8)
- [CVE-2017-8075](https://insights.sbomify.com/CVE-2017-8075/): Information disclosure in n/a (critical 9.8)
- [CVE-2017-8076](https://insights.sbomify.com/CVE-2017-8076/): Weak cryptography in n/a (critical 9.8)
- [CVE-2017-8077](https://insights.sbomify.com/CVE-2017-8077/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2017-17746](https://insights.sbomify.com/CVE-2017-17746/): Auth bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0730 and fix it if it is affected.

What it is: CVE-2025-0730 is a medium-severity vulnerability in TP-Link TL-SG108E, published on 27 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0730 in the wild and no public exploit code.

Affected product: TP-Link TL-SG108E. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-0730/ (Markdown: https://insights.sbomify.com/CVE-2025-0730/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0730
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0730
- OSV: https://osv.dev/vulnerability/CVE-2025-0730

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-0730/
Summaries are generated and may contain mistakes; the official description above is the record.