# CVE-2024-1490: Wago: Vulnerability in WBM through Open VPN

> Authenticated high-privilege attackers can execute arbitrary shell commands on WAGO PLCs via OpenVPN if user-defined scripts are enabled.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2026
- **Updated:** 9 Apr 2026
- **Also known as:** GHSA-4p2f-67g5-7xhf

## What is CVE-2024-1490?

CVE-2024-1490 is a high-severity command injection vulnerability in WAGO CC100 (0751-9x01), published on 9 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An authenticated remote attacker with high privileges can exploit the OpenVPN configuration via the web-based management interface of a WAGO PLC. If user-defined scripts are permitted, OpenVPN may allow the execution of arbitrary shell commands enabling the attacker to run arbitrary commands on the device.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-1490?


## How do I fix CVE-2024-1490?

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

## Is CVE-2024-1490 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1490 and fix it if it is affected.

What it is: CVE-2024-1490 is a high-severity command injection vulnerability in WAGO CC100 (0751-9x01), published on 9 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1490 in the wild and no public exploit code.

Affected product: WAGO CC100 (0751-9x01). 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-2024-1490/ (Markdown: https://insights.sbomify.com/CVE-2024-1490/index.md)
```

## Sources

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

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