# CVE-2019-25470: eWON Firmware 12.2-13.0 Authentication Bypass via wsdReadForm

> Attackers can bypass authentication to extract encrypted user passwords from eWON devices using a hardcoded key, leading to potential account takeover.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-jcxq-mj3r-cxrh

## What is CVE-2019-25470?

CVE-2019-25470 is a high-severity authentication bypass vulnerability in eWON, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

eWON Firmware versions 12.2 to 13.0 contain an authentication bypass vulnerability that allows attackers with minimal privileges to retrieve sensitive user data by exploiting the wsdReadForm endpoint. Attackers can send POST requests to /wrcgi.bin/wsdReadForm with base64-encoded partial credentials and a crafted wsdList parameter to extract encrypted passwords for all users, which can be decrypted using a hardcoded XOR key.

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

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


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

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

## Is CVE-2019-25470 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25470 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25470 is a high-severity authentication bypass vulnerability in eWON, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25470 exists.

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

## Sources

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

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