# CVE-2025-15092: UTT 进取 512W ConfigExceptMSN strcpy buffer overflow

> Remote attackers can trigger a buffer overflow in the UTT 512W router via the ConfigExceptMSN interface, potentially leading to code execution.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Dec 2025
- **Updated:** 26 Dec 2025
- **Also known as:** GHSA-q45h-4pv4-p744

## What is CVE-2025-15092?

CVE-2025-15092 is a high-severity memory corruption vulnerability in UTT 进取 512W, published on 26 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in UTT 进取 512W up to 1.7.7-171114. Impacted is the function strcpy of the file /goform/ConfigExceptMSN. Such manipulation of the argument remark leads to buffer overflow. It is possible to launch the attack remotely. The exploit is publicly available and might be used.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Utt 512w Firmware.

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

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

## Is CVE-2025-15092 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15092 exists.

## Other vulnerabilities in UTT 进取 512W

- [CVE-2025-14534](https://insights.sbomify.com/CVE-2025-14534/): UTT 进取 512W Endpoint formNatStaticMap strcpy buffer overflow (critical 9.3)
- [CVE-2025-14535](https://insights.sbomify.com/CVE-2025-14535/): UTT 进取 512W formConfigFastDirectionW strcpy buffer overflow (critical 9.3)
- [CVE-2025-15428](https://insights.sbomify.com/CVE-2025-15428/): UTT 进取 512W formRemoteControl strcpy buffer overflow (high 8.7)
- [CVE-2025-15429](https://insights.sbomify.com/CVE-2025-15429/): UTT 进取 512W formConfigCliForEngineerOnly strcpy buffer overflow (high 8.7)
- [CVE-2025-15430](https://insights.sbomify.com/CVE-2025-15430/): UTT 进取 512W formFtpServerShareDirSelcet strcpy buffer overflow (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15092 is a high-severity memory corruption vulnerability in UTT 进取 512W, published on 26 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15092 exists.

Affected product: UTT 进取 512W. 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-15092/ (Markdown: https://insights.sbomify.com/CVE-2025-15092/index.md)
```

## Sources

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

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