# CVE-2020-11926: Information disclosure in n/a

> Unauthenticated attackers can retrieve device credentials and Wi-Fi keys via a web request, compromising network security.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-3v5g-chfr-w797

## What is CVE-2020-11926?

CVE-2020-11926 is a high-severity vulnerability in n/a, published on 7 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Luvion Grand Elite 3 Connect through 2020-02-25. Clients can authenticate themselves to the device using a username and password. These credentials can be obtained through an unauthenticated web request, e.g., for a JavaScript file. Also, the disclosed information includes the SSID and WPA2 key for the Wi-Fi network the device is connected to.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2020-11926?


## How do I fix CVE-2020-11926?

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

## Is CVE-2020-11926 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11926 and fix it if it is affected.

What it is: CVE-2020-11926 is a high-severity vulnerability in n/a, published on 7 Nov 2024. 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-2020-11926 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-2020-11926/ (Markdown: https://insights.sbomify.com/CVE-2020-11926/index.md)
```

## Sources

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

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