# CVE-2025-14750: External Control of Assumed-Immutable Web Parameter in Weintek cMT X Series HMI EasyWeb Service

> A low-privileged user can modify assumed-immutable web parameters to manipulate account-level privileges on Weintek cMT X Series HMIs.

- **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`)
- **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:** 22 Jan 2026
- **Updated:** 26 Jan 2026
- **Also known as:** GHSA-hfxh-j63h-2qhw

## What is CVE-2025-14750?

CVE-2025-14750 is a high-severity vulnerability in Weintek cMT-CTRL01, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The web application does not sufficiently verify inputs that are assumed to be immutable but are actually externally controllable. A low-privileged user can modify the parameters and potentially manipulate account-level privileges.

Weakness: CWE-472 (External Control of Assumed-Immutable Web Parameter)

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


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

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

## Is CVE-2025-14750 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14750 is a high-severity vulnerability in Weintek cMT-CTRL01, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14750 in the wild and no public exploit code.

Affected product: Weintek cMT-CTRL01. 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-14750/ (Markdown: https://insights.sbomify.com/CVE-2025-14750/index.md)
```

## Sources

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

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