# CVE-2024-13723: Checkmk NagVis Remote Code Execution

> An authenticated administrator can upload a malicious PHP file to Checkmk NagVis to achieve remote code execution.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Feb 2025
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-13723, GHSA-vg5c-jm85-v84v, UBUNTU-CVE-2024-13723

## What is CVE-2024-13723?

CVE-2024-13723 is a high-severity vulnerability in Checkmk NagVis, published on 4 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The "NagVis" component within Checkmk is vulnerable to remote code execution. An authenticated attacker with administrative level privileges is able to upload a malicious PHP file and modify specific settings to execute the contents of the file as PHP.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

Apply the vendor's patch.

## Is CVE-2024-13723 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13723 is a high-severity vulnerability in Checkmk NagVis, published on 4 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-13723 exists.

Affected product: Checkmk NagVis. 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-13723/ (Markdown: https://insights.sbomify.com/CVE-2024-13723/index.md)
```

## Sources

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

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