# CVE-2025-7060: Monitorr Installer mkdbajax.php input validation

> Monitorr installer allows improper input validation in the datadir argument, potentially enabling path traversal attacks during installation.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jul 2025
- **Updated:** 7 Jul 2025
- **Also known as:** GHSA-988v-c5fj-9c75

## What is CVE-2025-7060?

CVE-2025-7060 is a low-severity path traversal vulnerability in Monitorr, published on 4 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was found in Monitorr up to 1.7.6m. It has been classified as problematic. This affects an unknown part of the file assets/config/_installation/mkdbajax.php of the component Installer. The manipulation of the argument datadir leads to improper input validation. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Monitorr Monitorr.

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

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

## Is CVE-2025-7060 being exploited?

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

## Other vulnerabilities in Monitorr

- [CVE-2020-28872](https://insights.sbomify.com/CVE-2020-28872/): Auth bypass in n/a (critical 9.8)
- [CVE-2020-28871](https://insights.sbomify.com/CVE-2020-28871/): File upload in n/a (critical 9.8)
- [CVE-2023-26775](https://insights.sbomify.com/CVE-2023-26775/): File upload in n/a (high 7.8)
- [CVE-2023-26776](https://insights.sbomify.com/CVE-2023-26776/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7060 is a low-severity path traversal vulnerability in Monitorr, published on 4 Jul 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-2025-7060 exists.

Affected product: Monitorr. 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-7060/ (Markdown: https://insights.sbomify.com/CVE-2025-7060/index.md)
```

## Sources

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

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