CVE-2016-7067: Monit before version 5.20.0 is vulnerable to a cross site request forgery attack

Q: How do I fix CVE-2016-7067?

monit: upgrade to 5.20.0. Exact commands for each OS are on this page.

Q: Is CVE-2016-7067 being exploited?

CVE-2016-7067 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2016-7067 affect?

CVE-2016-7067 affects monit. Severity is medium (CVSS 6.5). Monit before version 5.20.0 is vulnerable to a cross site request forgery attack. Successful exploitation will enable an attacker to disable/enable all monitoring for a particular host or disable/enable monitoring for a specific service.

Q: How urgent is CVE-2016-7067?

Priority 48/100. Public exploit reference; Remotely exploitable, no login, no user action

This week

MEDIUM 6.5REMOTEUPGRADE

CVE-2016-7067 is a medium-severity flaw (CVSS 6.5) affecting monit. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Monit before version 5.20.0 is vulnerable to a cross site request forgery attack. Successful exploitation will enable an attacker to disable/enable all monitoring for a particular host or disable/enable monitoring for a specific service.

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Weakness	CWE-352
Published	2018-09-10
Last modified	2026-06-17

Publisher (CNA): Red Hat, Inc. · Vendor: mmonit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-09-10 14:29 UTCPublished CVE record published
2026-06-17 00:52 UTCUpdated Record last modified

mmonit monit UPGRADE

Affected: < 5.20.0

Fixed in: 5.20.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy monit || rpm -q monit || monit --version

2. UPGRADE to 5.20.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade monit

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade monit

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-7067?

monit: upgrade to 5.20.0. Exact commands for each OS are on this page.

Is CVE-2016-7067 being exploited?

CVE-2016-7067 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-7067 affect?

CVE-2016-7067 affects monit. Severity is medium (CVSS 6.5). Monit before version 5.20.0 is vulnerable to a cross site request forgery attack. Successful exploitation will enable an attacker to disable/enable all monitoring for a particular host or disable/enable monitoring for a specific service.

How urgent is CVE-2016-7067?

Priority 48/100. Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2022-26563 HIGH 8.8 UPGRADE An issue was discovered in Tildeslash Monit before 5.31.0, allows remote attackers to gain escilated privlidge
CVE-2019-11455 HIGH 8.1 UPGRADE MITIGATE A buffer over-read in Util_urlDecode in util.c in Tildeslash Monit before 5.25.3 allows a remote authenticated
CVE-2019-11454 MEDIUM 6.1 UPGRADE MITIGATE Persistent cross-site scripting (XSS) in http/cervlet.c in Tildeslash Monit before 5.25.3 allows a remote unau
CVE-2019-11393 CRITICAL 9.8 UPGRADE An issue was discovered in /admin/users/update in M/Monit before 3.7.3

References

← Back to latest CVEs