# CVE-2024-45372: Cross-site request forgery in MZK-DP300N

> Attackers can force logged-in users to perform unintended actions like changing passwords via CSRF on the MZK-DP300N web interface.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Sep 2024
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-37jm-q7wj-f2wc

## What is CVE-2024-45372?

CVE-2024-45372 is a medium-severity vulnerability in PLANEX COMMUNICATIONS INC. MZK-DP300N, published on 26 Sep 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

MZK-DP300N firmware versions 1.04 and earlier contains a cross-site request forger vulnerability. Viewing a malicious page while logging in to the web management page of the affected product may lead the user to perform unintended operations such as changing the login password, etc.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-45372?

It affects 1 product.


Products: Planex Mzk-Dp300n Firmware.

## How do I fix CVE-2024-45372?

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

## Is CVE-2024-45372 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45372 and fix it if it is affected.

What it is: CVE-2024-45372 is a medium-severity vulnerability in PLANEX COMMUNICATIONS INC. MZK-DP300N, published on 26 Sep 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-45372 in the wild and no public exploit code.

Affected product: PLANEX COMMUNICATIONS INC. MZK-DP300N. 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-2024-45372/ (Markdown: https://insights.sbomify.com/CVE-2024-45372/index.md)
```

## Sources

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

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