# CVE-2024-41716: Information disclosure in WindLDR

> Attackers with access to project files can extract cleartext credentials to manipulate or suspend PLCs and Operator Interfaces.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A: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:** 4 Sep 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-pq2c-46q4-qwg3

## What is CVE-2024-41716?

CVE-2024-41716 is a high-severity vulnerability in IDEC Corporation WindLDR, published on 4 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cleartext storage of sensitive information vulnerability exists in WindLDR and WindO/I-NV4. If this vulnerability is exploited, an attacker who obtained the product's project file may obtain user credentials of the PLC or Operator Interfaces. As a result, an attacker may be able to manipulate and/or suspend the PLC and Operator Interfaces by accessing or hijacking them.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 2 products.


Products: Idec Windldr, Idec Windo\/I-Nv4.

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

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

## Is CVE-2024-41716 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41716 is a high-severity vulnerability in IDEC Corporation WindLDR, published on 4 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41716 in the wild and no public exploit code.

Affected product: IDEC Corporation WindLDR. 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-41716/ (Markdown: https://insights.sbomify.com/CVE-2024-41716/index.md)
```

## Sources

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

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