# CVE-2025-2359: D-Link DIR-823G DDNS Service HNAP1 SetDDNSSettings improper authorization

> Remote attackers can bypass authorization in the DDNS service to modify settings on unsupported D-Link DIR-823G routers.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2025
- **Updated:** 17 Mar 2025
- **Also known as:** GHSA-qvh6-jh7v-8fmr

## What is CVE-2025-2359?

CVE-2025-2359 is a medium-severity missing authorization vulnerability in Dlink Dir-823g Firmware, published on 17 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in D-Link DIR-823G 1.0.2B05_20181207. Affected is the function SetDDNSSettings of the file /HNAP1/ of the component DDNS Service. The manipulation of the argument SOAPAction leads to improper authorization. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2025-2359?

It affects 1 product.


Products: Dlink Dir-823g Firmware.

## How do I fix CVE-2025-2359?

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

## Is CVE-2025-2359 being exploited?

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

## Other vulnerabilities in Dlink Dir-823g Firmware

- [CVE-2023-43235](https://insights.sbomify.com/CVE-2023-43235/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-43241](https://insights.sbomify.com/CVE-2023-43241/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-26612](https://insights.sbomify.com/CVE-2023-26612/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-26613](https://insights.sbomify.com/CVE-2023-26613/): Command injection in n/a (critical 9.8)
- [CVE-2023-26616](https://insights.sbomify.com/CVE-2023-26616/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2359 and fix it if it is affected.

What it is: CVE-2025-2359 is a medium-severity missing authorization vulnerability in Dlink Dir-823g Firmware, published on 17 Mar 2025. 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-2025-2359 exists.

Affected product: Dlink Dir-823g Firmware. 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-2025-2359/ (Markdown: https://insights.sbomify.com/CVE-2025-2359/index.md)
```

## Sources

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

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