# CVE-2019-10712: Hardcoded credentials in n/a

> Undocumented service access in WAGO PLC Web-GUI allows attackers to bypass authentication and gain unauthorized access to the device.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r6gg-5rm9-xp64

## What is CVE-2019-10712?

CVE-2019-10712 is a critical vulnerability in n/a, published on 7 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Web-GUI on WAGO Series 750-88x (750-330, 750-352, 750-829, 750-831, 750-852, 750-880, 750-881, 750-882, 750-884, 750-885, 750-889) and Series 750-87x (750-830, 750-849, 750-871, 750-872, 750-873) devices has undocumented service access.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2019-10712?

It affects 16 products.


Products: Wago 750-330 Firmware, Wago 750-352 Firmware, Wago 750-829 Firmware, Wago 750-830 Firmware, Wago 750-831 Firmware, Wago 750-849 Firmware, Wago 750-852 Firmware, Wago 750-871 Firmware, Wago 750-872 Firmware, Wago 750-873 Firmware, Wago 750-880 Firmware, Wago 750-881 Firmware, Wago 750-882 Firmware, Wago 750-884 Firmware, Wago 750-885 Firmware, Wago 750-889 Firmware.

## How do I fix CVE-2019-10712?

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

## Is CVE-2019-10712 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10712 and fix it if it is affected.

What it is: CVE-2019-10712 is a critical vulnerability in n/a, published on 7 May 2019. 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-2019-10712 in the wild and no public exploit code.

Affected product: n/a. 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-2019-10712/ (Markdown: https://insights.sbomify.com/CVE-2019-10712/index.md)
```

## Sources

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

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