CVE-2022-38254
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 · uneditedNagios XI before v5.8.7 was discovered to contain a cross-site scripting (XSS) vulnerability via the ajax.php script in CCM 3.1.5.
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 · high confidenceNagios XI versions prior to 5.8.7 contain a stored cross-site scripting (XSS) vulnerability in the ajax.php script within the Configuration Component Manager (CCM) version 3.1.5. An attacker can inject malicious JavaScript code through this endpoint, which will execute in the context of other users' browsers when they access the affected functionality.
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< 5.8.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine Nagios XI versionLog into the Nagios XI web interface and navigate to the Admin > System Information page, or run 'rpm -q nagiosxi' on the server command line to check the installed package versionAffected if The installed version is earlier than 5.8.7 (e.g., 5.8.6, 5.8.5, etc.)
-
Identify CCM versionAccess the Configuration Component Manager (CCM) via the web interface at /nagiosxi/ccm or check the CCM version information in the Nagios XI administration areaAffected if CCM version 3.1.5 is reported and the Nagios XI version is below 5.8.7
-
Locate ajax.php in CCMCheck for the presence of the CCM ajax.php script in the web directory, typically found at /usr/local/nagiosxi/html/nagiosxi/ccm/ajax.php or within the CCM web rootAffected if The ajax.php file exists in the CCM directory and the system version is below 5.8.7
-
Verify CCM is accessibleAttempt to access the CCM interface through the Nagios XI web portal to confirm the component is enabled and functionalAffected if CCM is accessible and the Nagios XI version is below 5.8.7
You are affected if your Nagios XI installation is version 5.8.6 or earlier AND the Configuration Component Manager (CCM) with ajax.php is accessible in your environment.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.8.7
Upgrade Nagios XI to version 5.8.7 or later to obtain the patch for this XSS vulnerability. Until then, consider restricting access to the CCM ajax.php endpoint or implementing WAF rules.
Nagios XI 5.8.7 or later
- Back up the Nagios XI database and configuration files before proceeding
- Download Nagios XI version 5.8.7 or later from the official Nagios website
- Run the Nagios XI upgrade installer according to official upgrade documentation
- Verify the upgrade was successful by logging into the Nagios XI interface
- Confirm the CCM (Core Configuration Manager) version is 3.1.6 or later which includes the XSS fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38254 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-38254 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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