CVE-2023-51072
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 · uneditedA stored cross-site scripting (XSS) vulnerability in the NOC component of Nagios XI version up to and including 2024R1 allows low-privileged users to execute malicious HTML or JavaScript code via the audio file upload functionality from the Operation Center section. This allows any authenticated user to execute arbitrary JavaScript code on behalf of other users, including the administrators.
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 confidenceA stored cross-site scripting vulnerability exists in the NOC (Network Operations Center) component of Nagios XI, specifically in the audio file upload functionality within the Operation Center section. Authenticated low-privilege users can upload files containing malicious HTML or JavaScript code that executes when viewed by other users, including administrators.
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< 2024= 2024CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify Nagios XI installation and versionAccess the Nagios XI administration interface and navigate to the Help > About section, or run 'rpm -q nagiosxi' or 'cat /usr/local/nagiosxi/etc/xi-sys.cfg' to determine the installed versionAffected if The installed version is either older than 2024 or exactly 2024
-
Verify NOC/Operation Center component accessLog into the Nagios XI web interface and navigate to the Operation Center section (usually found under the NOC menu or similar) to confirm the component is accessibleAffected if The Operation Center section is accessible and the audio upload functionality is present
-
Check audio upload functionality permissionsNavigate to the Operation Center audio upload feature and attempt to access it with a low-privilege user account, or review the user role permissions for audio file uploads in the system configurationAffected if Low-privilege authenticated users can access or are permitted to use the audio file upload feature in Operation Center
-
Inspect existing audio files for potentially malicious contentLocate the audio file storage directory (typically under /usr/local/nagiosxi/media/audio/ or similar upload directories) and examine uploaded .html, .htm, .js files or audio files containing suspicious HTML/script tags in metadata or embedded contentAffected if Audio files containing HTML script tags, JavaScript code, or other executable content are present in the upload directory
-
Review upload activity logsCheck Nagios XI logs for audio file upload events in the Operation Center section, looking for uploads from low-privilege users that may contain unexpected file types or contentAffected if Low-privilege users have successfully uploaded files to the audio upload functionality, particularly non-audio file types
Your environment is affected if you are running Nagios XI version 2024 or earlier and the Operation Center audio upload feature is accessible to low-privilege authenticated users.
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 · scoped2024
Implement strict input validation and sanitization for file uploads, including file type verification, content inspection, and sanitization of any metadata that could contain scriptable content. Consider restricting or limiting the audio upload functionality to trusted user roles.
Nagios XI version newer than 2024R1 (check www.nagios.com for the latest stable release)
- 1. Back up the current Nagios XI installation, including the database and configuration files
- 2. Download the latest Nagios XI version from the official Nagios website (www.nagios.com)
- 3. Review the upgrade instructions specific to your current version in the official documentation
- 4. Execute the upgrade process following Nagios official upgrade procedures
- 5. After upgrade, verify the audio file upload functionality in the NOC/Operation Center section now properly validates and sanitizes uploaded files
- 6. Confirm the XSS vulnerability is remediated by attempting to upload a file with malicious content (or verify via security testing)
- 7. Test that legitimate audio file uploads still function correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51072 — 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-2023-51072 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