# CVE-2019-13560: Auth bypass in n/a

> Remote attackers can force a blank password on D-Link DIR-655 C devices via the setup wizard, leading to unauthorized access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jp5g-jhw5-m355

## What is CVE-2019-13560?

CVE-2019-13560 is a critical authentication bypass vulnerability in n/a, published on 11 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link DIR-655 C devices before 3.02B05 BETA03 allow remote attackers to force a blank password via the apply_sec.cgi setup_wizard parameter.

Weakness: CWE-255

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

It affects 1 product.


Products: Dlink Dir-655 Firmware.

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

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

## Is CVE-2019-13560 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-13561](https://insights.sbomify.com/CVE-2019-13561/): Command injection in n/a (critical 9.8)
- [CVE-2019-13563](https://insights.sbomify.com/CVE-2019-13563/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2025-6158](https://insights.sbomify.com/CVE-2025-6158/): D-Link DIR-665 HTTP POST Request sub_AC78 stack-based overflow (high 8.7)
- [CVE-2019-13562](https://insights.sbomify.com/CVE-2019-13562/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-13560 is a critical authentication bypass vulnerability in n/a, published on 11 Jul 2019. 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-2019-13560 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-2019-13560/ (Markdown: https://insights.sbomify.com/CVE-2019-13560/index.md)
```

## Sources

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

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