# CVE-2018-6530: D-Link Multiple Routers OS Command Injection

> Remote attackers can execute arbitrary OS commands on D-Link routers via the service parameter in soap.cgi.

- **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:** Yes, since 8 Sep 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2018
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-j95f-33m4-87jf

## What is CVE-2018-6530?

CVE-2018-6530 is a critical command injection vulnerability in n/a, published on 6 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OS command injection vulnerability in soap.cgi (soapcgi_main in cgibin) in D-Link DIR-880L DIR-880L_REVA_FIRMWARE_PATCH_1.08B04 and previous versions, DIR-868L DIR868LA1_FW112b04 and previous versions, DIR-65L DIR-865L_REVA_FIRMWARE_PATCH_1.08.B01 and previous versions, and DIR-860L DIR860LA1_FW110b04 and previous versions allows remote attackers to execute arbitrary OS commands via the service parameter.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 4 products.


Products: Dlink Dir-860l Firmware, Dlink Dir-865l Firmware, Dlink Dir-868l Firmware, Dlink Dir-880l Firmware.

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

No fix has been published for CVE-2018-6530 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 29 Sep 2022.

## Is CVE-2018-6530 being exploited?

Yes. Attackers have exploited CVE-2018-6530 in the wild since at least 8 Sep 2022, including in ransomware campaigns.

Public exploit code:

- D-Link - Unauthenticated Remote Code Execution (nuclei): http/cves/2018/CVE-2018-6530.yaml

## Other vulnerabilities in n/a

- [CVE-2024-42812](https://insights.sbomify.com/CVE-2024-42812/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-41611](https://insights.sbomify.com/CVE-2024-41611/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-9026](https://insights.sbomify.com/CVE-2025-9026/): D-Link DIR-860L Simple Service Discovery Protocol cgibin ssdpcgi_main os command injection (medium 6.9)
- [CVE-2024-37605](https://insights.sbomify.com/CVE-2024-37605/): Null dereference in n/a (medium 6.5)
- [CVE-2018-6527](https://insights.sbomify.com/CVE-2018-6527/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-6530 is a critical command injection vulnerability in n/a, published on 6 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2018-6530 in the wild since at least 8 Sep 2022, including in ransomware campaigns.

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

## Sources

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

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