CVE-2023-7321
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 Log Server versions prior to 2.1.14 are vulnerable to cross-site scripting (XSS) via the Snapshots Page. Untrusted log content was not safely encoded for the output context, allowing attacker-controlled data present in logs to execute script in the victim’s browser within the application origin.
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 Log Server versions prior to 2.1.14 fail to properly encode untrusted log content displayed on the Snapshots Page, allowing attacker-controlled data embedded in logs to execute arbitrary JavaScript in authenticated users' browsers (stored XSS).
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< 2.1.14CVSS 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 Log Server installationLocate the Nagios Log Server installation directory or check running services for the Nagios Log Server processAffected if Nagios Log Server is installed and running
-
Determine installed versionCheck the installed Nagios Log Server version using the product's web interface (typically found in the Help/About section) or by querying the installed package/version fileAffected if Version is below 2.1.14 (any version prior to 2.1.14 is affected)
-
Verify Snapshots feature accessConfirm the Snapshots page functionality is accessible in the Nagios Log Server web interfaceAffected if Authenticated users can access the Snapshots page feature
-
Assess log ingestion sourcesReview configured log sources and ingestion endpoints to determine if untrusted or external data is being processedAffected if Logs from untrusted or attacker-controlled sources are being ingested into the system
A user is affected if Nagios Log Server version is below 2.1.14 AND the Snapshots feature is accessible AND the system processes logs from untrusted sources that could contain malicious JavaScript payload.
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 · scoped2.1.14
Upgrade to Nagios Log Server version 2.1.14 or later which includes proper output encoding. Until upgraded, restrict log ingestion to trusted sources and consider disabling the Snapshots feature if feasible.
2.1.14
- Check the current Nagios Log Server version via the administrative interface or system commands
- Back up the entire Nagios Log Server installation including configuration files and databases
- Download Nagios Log Server version 2.1.14 or later from the official Nagios downloads page
- Follow the official Nagios Log Server upgrade procedure to apply the update
- After upgrade, verify the Snapshots Page now safely encodes log content to prevent XSS
- Confirm normal application functionality after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-7321 — 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-7321 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