# CVE-2019-25249: devolo dLAN 500 AV Wireless+ 3.1.0-1 Remote Code Execution via htmlmgr

> Attackers can bypass authentication to enable hidden services and gain root access on devolo dLAN devices.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:** 24 Dec 2025
- **Updated:** 24 Dec 2025
- **Also known as:** GHSA-p782-2pf9-qvmm

## What is CVE-2019-25249?

CVE-2019-25249 is a high-severity authentication bypass vulnerability in devolo AG dLAN 550 duo+ Starter Kit, published on 24 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

devolo dLAN 500 AV Wireless+ 3.1.0-1 contains an authentication bypass vulnerability that allows attackers to enable hidden services through the htmlmgr CGI script. Attackers can enable telnet and remote shell services, reboot the device, and gain root access without a password by manipulating system configuration parameters.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2019-25249 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25249 is a high-severity authentication bypass vulnerability in devolo AG dLAN 550 duo+ Starter Kit, published on 24 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25249 exists.

Affected product: devolo AG dLAN 550 duo+ Starter Kit. 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-25249/ (Markdown: https://insights.sbomify.com/CVE-2019-25249/index.md)
```

## Sources

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

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