# CVE-2025-6932: D-Link DCS-7517 Qlync Password Generation httpd g_F_n_GenPassForQlync hard-coded password

> Attackers can exploit a hard-coded password in the Qlync password generation handler to potentially take over accounts on unsupported D-Link cameras.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2025
- **Updated:** 1 Jul 2025
- **Also known as:** GHSA-h8vc-h8jx-g4wf

## What is CVE-2025-6932?

CVE-2025-6932 is a medium-severity vulnerability in D-Link DCS-7517, published on 30 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, was found in D-Link DCS-7517 up to 2.02.0. This affects the function g_F_n_GenPassForQlync of the file /bin/httpd of the component Qlync Password Generation Handler. The manipulation leads to use of hard-coded password. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-259 (Use of Hard-coded Password), CWE-255

## Which versions are affected by CVE-2025-6932?

It affects 1 product.


Products: Dlink Dcs-7517 Firmware.

## How do I fix CVE-2025-6932?

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

## Is CVE-2025-6932 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6932 and fix it if it is affected.

What it is: CVE-2025-6932 is a medium-severity vulnerability in D-Link DCS-7517, published on 30 Jun 2025. 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-2025-6932 in the wild and no public exploit code.

Affected product: D-Link DCS-7517. 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-2025-6932/ (Markdown: https://insights.sbomify.com/CVE-2025-6932/index.md)
```

## Sources

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

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