dbcve.org
Pandora FmsApplication · Pandorafms

CVE-2023-44089

MEDIUM · 6.1 CVSS v3.1 Published 2023-12-29
Fix available
A fix is available. Upgrade to after 774 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Pandora FMS on all allows Cross-Site Scripting (XSS). It was possible to execute malicious JS code on Visual Consoles. This issue affects Pandora FMS: from 700 through 774.

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 confidence

A stored Cross-Site Scripting (XSS) vulnerability exists in Pandora FMS Visual Consoles where user-supplied input is not properly sanitized before being rendered in web pages, allowing execution of arbitrary JavaScript code in the context of other users' sessions.

MitigationImplement proper output encoding/sanitization for all user input rendered in Visual Consoles, and consider adding Content Security Policy (CSP) headers to mitigate XSS 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
Pandora FmsApplication
Affected:>= 700, <= 774

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. Check installed Pandora FMS version
    Access the Pandora FMS web console and navigate to 'Operation' > 'General' > 'System info' to view the exact version number, or run the command 'pandora_server -v' on the server CLI
    Affected if The displayed version falls within the range >= 700 and <= 774
  2. Verify Visual Consoles module is accessible
    Log into Pandora FMS and attempt to access the Visual Consoles section via 'Visual Consoles' in the main menu, or check the URL pattern '/pandora_console/index.php?sec=godmode&sec2=godmode/vconsoles'
    Affected if The Visual Consoles interface loads and is accessible to your user account
  3. Identify existing Visual Console configurations
    Navigate to 'Visual Consoles' > 'Manage Visual Consoles' and list all created consoles, or query the database table 'tvisual_console' for records
    Affected if Any Visual Console exists in the system, as stored XSS payloads would be embedded within user-created console content
  4. Inspect Visual Console element configurations
    Edit each Visual Console and examine the properties of added elements (text labels, URLs, descriptions), or examine the tvisual_console_element table for raw content
    Affected if User-supplied values in element properties are rendered without visible sanitization or encoding when the console is displayed

You are affected if your Pandora FMS version is between 700 and 774 inclusive AND you have any Visual Consoles configured, as the stored XSS payload will execute when other users view those consoles.

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 774
Interim mitigation

Implement proper output encoding/sanitization for all user input rendered in Visual Consoles, and consider adding Content Security Policy (CSP) headers to mitigate XSS attacks.

Recommended fix Moderate confidence

Upgrade to Pandora FMS version > 774 (latest stable release)

  1. Backup the current Pandora FMS database and configuration files
  2. Download or access the latest Pandora FMS version from the official vendor repository (pandorafms.com)
  3. Ensure the target version is newer than 774 to include the security fix
  4. Stop the Pandora FMS services (pandora_server and tentacle_server)
  5. Upgrade the Pandora FMS installation using the appropriate method for your setup (package manager, manual upgrade, or Docker)
  6. Start the Pandora FMS services
  7. Verify the Visual Console functionality works correctly and the XSS vulnerability is resolved
Caveat Review release notes for version 775+ for any database schema changes or configuration updates that may require attention before upgrading

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

Fix this in Pandora Fms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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