dbcve.org
Pandora FmsApplication · Pandorafms

CVE-2023-24514

MEDIUM · 6.1 CVSS v3.1 Published 2023-08-22
Fix available
A fix is available. Upgrade to after 767 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-site Scripting (XSS) vulnerability in Visual Console Module of Pandora FMS could be used to hijack admin users session cookie values, carry out phishing attacks, etc. This issue affects Pandora FMS v767 version and prior versions on all platforms.

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

A Cross-site Scripting (XSS) vulnerability exists in the Visual Console Module of Pandora FMS. This vulnerability allows attackers to inject malicious scripts that can hijack admin user session cookie values, enabling session takeover and phishing attacks against administrative users.

MitigationImplement proper input validation and output encoding in the Visual Console Module to neutralize malicious script payloads. Additionally, configure HttpOnly and Secure flags on session cookies to prevent theft via 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
Pandora FmsApplication
Affected:<= 767

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

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

  1. Identify Pandora FMS installation
    Locate the Pandora FMS installation directory or check system services for pandora processes (e.g., ps aux | grep pandora, or look for /var/www/html/pandora_ajax.php common web root)
    Affected if Pandora FMS software is present on the system
  2. Determine installed Pandora FMS version
    Check the version file or admin interface: look for a VERSION file in the installation directory, or log into the web admin panel and check 'Admin Tools > Setup > General' for the version number
    Affected if The installed version is 767 or earlier (any version <= 767)
  3. Verify Visual Console Module is accessible
    Check if the Visual Console feature is enabled and accessible by navigating to the web interface or examining configuration files for module status (look for 'visual_console' or 'vnstat' related entries in config files)
    Affected if The Visual Console Module is enabled and accessible to users
  4. Inspect Visual Console configuration for injection points
    Review the Visual Console module configuration files in the pandora installation for unsanitized user-supplied parameters, or test the Visual Console input fields with benign characters to observe if they are reflected without encoding
    Affected if Visual Console accepts user input without proper input validation or outputs data without encoding

You are affected if your Pandora FMS installation is version 767 or earlier AND the Visual Console Module is enabled and accessible, as this creates the conditions for XSS exploitation.

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 a release after 767
Interim mitigation

Implement proper input validation and output encoding in the Visual Console Module to neutralize malicious script payloads. Additionally, configure HttpOnly and Secure flags on session cookies to prevent theft via XSS.

Recommended fix Moderate confidence

v768 or later (latest stable release)

  1. 1. Identify current Pandora FMS version by checking the system information or administration panel
  2. 2. Perform a complete backup of the Pandora FMS database and configuration files
  3. 3. Download and install Pandora FMS v768 or later from the official Pandora FMS repository or website
  4. 4. Follow the official upgrade documentation for your specific platform to complete the migration
  5. 5. After upgrade, verify the Visual Console Module no longer accepts unsanitized input by testing with benign script payloads
  6. 6. Confirm admin session cookies are properly handled with HttpOnly and Secure flags

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

Fix this in Pandora Fms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-24514 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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