dbcve.org
MonitorixApplication · Fibranet

CVE-2018-7649

MEDIUM · 6.1 CVSS v3.0 Published 2018-08-02
Fix available
A fix is available. Upgrade to 3.10.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Monitorix before 3.10.1 allows XSS via CGI variables.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Monitorix before 3.10.1 contains a cross-site scripting (XSS) vulnerability in its CGI web interface. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized CGI variables, which are then executed in the browsers of users accessing the affected CGI scripts.

MitigationUpgrade Monitorix to version 3.10.1 or later to obtain the patch. Alternatively, implement input validation and output encoding for all CGI variable inputs to prevent XSS execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MonitorixApplication
Affected:< 3.10.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Monitorix installation path
    Common locations include /etc/monitorix/, /usr/share/monitorix/, or check your package manager listing (rpm -qa | grep monitorix or dpkg -l | grep monitorix)
    Affected if The installed version is found to be below 3.10.1
  2. Identify the Monitorix version
    Run: monitorix -v OR check /usr/share/monitorix/VERSION file OR look at package version if installed via package manager
    Affected if Version returned is lower than 3.10.1
  3. Verify CGI interface is enabled
    Check monitorix.conf for 'enable_cgilog' set to 1 or 'cgi' section with 'enable' set to 1; also verify Apache/Nginx config includes Monitorix CGI scripts (typically in /cgi-bin/)
    Affected if CGI web interface is enabled and accessible via HTTP/HTTPS
  4. Confirm web server exposes Monitorix CGI scripts
    Check web server configuration (Apache: /etc/httpd/conf.d/monitorix.conf, Nginx: monitorix.conf includes CGI location) and attempt to access http://yourhost/cgi-bin/monitorix.cgi
    Affected if The CGI scripts are reachable over the network without authentication

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 3.10.1 or later
Fixed in 3.10.1
Interim mitigation

Upgrade Monitorix to version 3.10.1 or later to obtain the patch. Alternatively, implement input validation and output encoding for all CGI variable inputs to prevent XSS execution.

Fix this in Monitorix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7649 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-7649 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data