CVE-2022-29269
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 · uneditedIn Nagios XI through 5.8.5, in the schedule report function, an authenticated attacker is able to inject HTML tags that lead to the reformatting/editing of emails from an official email address.
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 through 5.8.5 contain a stored Cross-Site Scripting (XSS) vulnerability in the schedule report function. An authenticated attacker with access to this feature can inject arbitrary HTML tags into report configurations, which then get rendered in emails sent from the system, allowing manipulation of email content formatting and potentially enabling further client-side attacks.
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.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Identify Nagios XI installation and versionAccess the Nagios XI web interface and navigate to the Admin > System Information page, or run 'cat /usr/local/nagiosxi/var/xi-version.txt' from the server command line to determine the installed version numberAffected if The installed version is 5.8.5 or lower (<= 5.8.5)
-
Verify schedule report feature accessLog into Nagios XI with an authenticated account and navigate to the Reports > Scheduled Reports section to confirm the feature is accessibleAffected if The schedule report feature is available and the user has permissions to create or modify scheduled reports
-
Inspect scheduled report configurations for injected contentIn the Nagios XI web interface, go to Reports > Scheduled Reports and examine existing report configurations. Check all text fields (report names, descriptions, recipient fields) for unexpected HTML tags such as <script>, <iframe>, <img>, or other HTML markupAffected if Any scheduled report configuration contains raw HTML tags or suspicious markup that was not intentionally entered by an administrator
-
Review email logs for manipulated contentExamine email logs or sent emails originating from Nagios XI (check mail server logs or email quarantine) for messages with unexpected formatting, embedded links, or content that appears to have been injected via HTML tag injectionAffected if Emails sent from the scheduled report feature contain unexpected HTML content or appear to have been manipulated
A system is affected if it runs Nagios XI version 5.8.5 or lower AND has the scheduled report feature accessible to authenticated users, with potential indicators being HTML markup found in report configurations or sent emails.
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 · scopedImplement robust input validation and output encoding on all user-supplied content in the schedule report feature to prevent HTML tag injection. Update to vendor patches addressing this vulnerability in Nagios XI.
Nagios XI 5.8.6 or later (ensure you upgrade to the version that includes the security fix for CVE-2022-29269)
- 1. Identify your current Nagios XI version by navigating to Admin > System Information in the web interface
- 2. Back up your Nagios XI configuration and database before performing any upgrade
- 3. Download the latest Nagios XI version from the official Nagios website (www.nagios.com) or the official Nagios XI download page
- 4. Run the standard Nagios XI update script: ./upgrade_xl or use the web-based update mechanism
- 5. After upgrade completion, verify the version number reflects the fixed release
- 6. Test the schedule report functionality to confirm the XSS vulnerability is remediated
- 7. Clear browser cache and test with a non-privileged account to confirm the fix prevents HTML injection in the schedule report function
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29269 — 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-29269 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