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

> The MailConnect feature allows attackers to perform Server-Side Request Forgery by connecting to arbitrary internal hosts and ports.

- **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hq7j-8qv3-mmrm

## What is CVE-2018-15517?

CVE-2018-15517 is a high-severity server-side request forgery vulnerability in n/a, published on 31 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The MailConnect feature on D-Link Central WiFiManager CWM-100 1.03 r0098 devices is intended to check a connection to an SMTP server but actually allows outbound TCP to any port on any IP address, leading to SSRF, as demonstrated by an index.php/System/MailConnect/host/127.0.0.1/port/22/secure/ URI.

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

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

It affects 1 product.


Products: Dlink Central Wifimanager.

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

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

## Is CVE-2018-15517 being exploited?

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

Public exploit code:

- D-Link Central WifiManager - Server-Side Request Forgery (nuclei): http/cves/2018/CVE-2018-15517.yaml

## 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-15517 and fix it if it is affected.

What it is: CVE-2018-15517 is a high-severity server-side request forgery vulnerability in n/a, published on 31 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-15517 exists.

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-15517/ (Markdown: https://insights.sbomify.com/CVE-2018-15517/index.md)
```

## Sources

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

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