Skip to main content
CVE-2025-7060VulnerabilityPublished Updated

CVE-2025-7060: Monitorr · Improper Input Validation

Affects MonitorrSource CVE Database V5

0

Not known to be exploited · CVSS 2.1 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
2.1Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
MonitorrAffected
  • =1.7.6
  • <=1.7.6
Fixed in–

AI-suggested

1. Restrict access to the installation directories and scripts, ensuring that only trusted administrators can execute or modify installation components. 2. Implement strict file system permissions on assets/config/_installation/mkdbajax.php to prevent unauthorized reading or writing. 3. Conduct installation and upgrade procedures in isolated, secure environments to minimize exposure during these phases. 4. Monitor and audit installation activities and logs for unusual or unauthorized input parameters related to 'datadir' or other configuration arguments. 5. If possible, review and sanitize input parameters manually or via custom scripts before running the installer to ensure no malicious input is processed. 6. Consider deploying network segmentation and access controls to limit remote access to installation interfaces. 7. Stay alert for vendor updates or community patches addressing this vulnerability and apply them promptly once available. 8. As a longer-term measure, evaluate alternative monitoring solutions or updated versions of Monitorr that do not exhibit this vulnerability.

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.

References

Community reviews

Loading reviews…