Log ServerApplication · Nagios

CVE-2023-7323

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 2024 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Log Server versions prior to 2024R1 are vulnerable to cross-site scripting (XSS) via the Create User function. Insufficient validation or escaping of user-supplied input may allow an attacker to inject and execute arbitrary script in the context of a victim's browser.

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 Log Server versions prior to 2024R1 contain a stored cross-site scripting (XSS) vulnerability in the Create User function. The application fails to properly validate or escape user-supplied input, allowing an attacker to inject malicious JavaScript that executes in the context of other users' browsers.

MitigationUpgrade to Nagios Log Server 2024R1 or later to obtain the patch that properly validates and escapes user input in the Create User function.

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
Log ServerApplication
Affected:< 2024

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Nagios Log Server version
    Access the Nagios Log Server admin interface and navigate to the About or System Information page to view the installed version number. Alternatively, check the version via command line if you have server access.
    Affected if The installed version is earlier than 2024R1 (any version in the 2023.x series or earlier).
  2. Confirm Create User functionality exists
    Log into the Nagios Log Server web interface and navigate to the User Administration or Users section to verify the Create User function is present and accessible.
    Affected if The Create User function is available in the interface, indicating the vulnerable feature is exposed.
  3. Review existing user accounts for injected scripts
    In the User Administration section, inspect all user account names, display names, email addresses, and other user-provided fields for unusual characters or patterns that may indicate XSS payloads (such as <script> tags, javascript: URIs, or event handlers like onload/onerror).
    Affected if Any user account contains suspicious input that could be malicious JavaScript, indicating potential exploitation.

You are affected if your Nagios Log Server version is prior to 2024R1 and the Create User function is accessible, or if you discover user accounts containing potentially malicious script content.

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
Upgrade available Upgrade to 2024 or later
Fixed in 2024
Interim mitigation

Upgrade to Nagios Log Server 2024R1 or later to obtain the patch that properly validates and escapes user input in the Create User function.

Recommended fix High confidence

2024R1

  1. 1. Back up your current Nagios Log Server configuration and data
  2. 2. Download the latest Nagios Log Server version 2024R1 from the official Nagios website (www.nagios.com)
  3. 3. Follow the official upgrade instructions for Nagios Log Server
  4. 4. Verify the upgrade was successful by logging into the web interface
  5. 5. Test the Create User function to confirm XSS vulnerability is remediated
Caveat Review release notes for any configuration changes or migration steps required when upgrading to 2024R1

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

Fix this in Log Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-7323 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-7323 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