dbcve.org
Nagios XiApplication · Nagios

CVE-2022-38249

MEDIUM · 6.1 CVSS v3.1 Published 2022-09-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Nagios XI v5.8.6 was discovered to contain a cross-site scripting (XSS) vulnerability via the MTR component in version 1.0.4.

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

Nagios XI v5.8.6 contains a stored cross-site scripting (XSS) vulnerability in the MTR component (version 1.0.4). The vulnerability allows attackers to inject malicious JavaScript code through user-supplied input that is rendered without proper sanitization or output encoding.

MitigationImplement input validation and output encoding/sanitization for all user-supplied data in the MTR component, or update to a patched version of the MTR component if available.

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
Nagios XiApplication
Affected:= 5.8.6

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.1/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. Confirm Nagios XI version
    Access the web interface and navigate to 'Admin' > 'System Information' or run 'cat /usr/local/nagiosxi/var/xi-sys.cfg' to check the installed version
    Affected if The installed version is exactly 5.8.6
  2. Verify MTR component installation
    Navigate to the MTR component in Nagios XI (typically under 'Configure' > 'MTR' or check the component directory at /usr/local/nagiosxi/html/includes/components/mtr/) and check the version file or about page
    Affected if The MTR component version is 1.0.4
  3. Identify vulnerable input fields
    Access the MTR component interface and locate input fields where users can enter data (such as target hosts, parameters, or labels) that gets stored and displayed back
    Affected if User-supplied input fields exist in the MTR component without apparent input validation indicators
  4. Inspect stored MTR data for XSS payloads
    Check the database or configuration files where MTR component stores user input (typically in the nagiosxi database, table like mtr_targets or similar) for any unexpected script tags or JavaScript content
    Affected if Stored data contains unsanitized HTML or JavaScript tags that would execute in a browser

A user is affected if Nagios XI version 5.8.6 is running with the MTR component version 1.0.4 and user-supplied input in MTR is rendered without sanitization.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement input validation and output encoding/sanitization for all user-supplied data in the MTR component, or update to a patched version of the MTR component if available.

Recommended fix Moderate confidence

Nagios XI version 5.8.7 or later (check release notes for exact fixed version)

  1. Check current Nagios XI version by navigating to Admin > System Information in the XI interface
  2. Verify the MTR component version is 1.0.4 by reviewing installed components
  3. Contact Nagios support or check Nagios XI release notes for version 5.8.7 or later which should contain the security fix
  4. Upgrade to the fixed Nagios XI version following standard upgrade procedures
  5. After upgrade, verify the MTR component has been updated to a version later than 1.0.4
  6. Test that the XSS vulnerability is no longer reproducible
Caveat Review Nagios XI release notes for any configuration or feature changes between 5.8.6 and the fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nagios Xi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38249 — 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-2022-38249 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