# CVE-2015-2050: Command injection in n/a

> Attackers can execute arbitrary commands on D-Link DAP-1320 access points, potentially compromising the device.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 23 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wvmw-mw98-5g36

## What is CVE-2015-2050?

CVE-2015-2050 is a critical command injection vulnerability in n/a, published on 23 Feb 2015. It can be exploited over the network.

### Official description

D-Link DAP-1320 Rev Ax with firmware before 1.21b05 allows attackers to execute arbitrary commands via unspecified vectors.

## Which versions are affected by CVE-2015-2050?

It affects 1 product.


Products: Dlink Dap-1320 Firmware.

## How do I fix CVE-2015-2050?

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

## Is CVE-2015-2050 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-1538](https://insights.sbomify.com/CVE-2025-1538/): D-Link DAP-1320 api set_ws_action heap-based overflow (high 8.7)
- [CVE-2025-1539](https://insights.sbomify.com/CVE-2025-1539/): D-Link DAP-1320 storagein.pd-XXXXXX replace_special_char stack-based overflow (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2050 and fix it if it is affected.

What it is: CVE-2015-2050 is a critical command injection vulnerability in n/a, published on 23 Feb 2015. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2015-2050 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-2015-2050/ (Markdown: https://insights.sbomify.com/CVE-2015-2050/index.md)
```

## Sources

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

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