# CVE-2018-15516: Server-side request forgery in n/a

> Remote attackers can exploit the FTP service to conduct bounce scans via SSRF, potentially bypassing network restrictions and accessing internal resources.

- **Severity:** Medium 5.8 (`CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h6pf-c244-8chr

## What is CVE-2018-15516?

CVE-2018-15516 is a medium-severity server-side request forgery vulnerability in n/a, published on 31 Jan 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The FTP service on D-Link Central WiFiManager CWM-100 1.03 r0098 devices allows remote attackers to conduct a PORT command bounce scan via port 8000, resulting in SSRF.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2018-15516?

It affects 1 product.


Products: Dlink Central Wifimanager.

## How do I fix CVE-2018-15516?

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

## Is CVE-2018-15516 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-13372](https://insights.sbomify.com/CVE-2019-13372/): Code injection in n/a (critical 9.8)
- [CVE-2019-13373](https://insights.sbomify.com/CVE-2019-13373/): SQL injection in n/a (critical 9.8)
- [CVE-2019-13375](https://insights.sbomify.com/CVE-2019-13375/): SQL injection in n/a (critical 9.8)
- [CVE-2018-17440](https://insights.sbomify.com/CVE-2018-17440/): File upload in n/a (critical 9.8)
- [CVE-2018-17442](https://insights.sbomify.com/CVE-2018-17442/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-15516 and fix it if it is affected.

What it is: CVE-2018-15516 is a medium-severity server-side request forgery vulnerability in n/a, published on 31 Jan 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-15516 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-2018-15516/ (Markdown: https://insights.sbomify.com/CVE-2018-15516/index.md)
```

## Sources

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

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