dbcve.org
Pandora FmsApplication · Artica

CVE-2023-41789

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-23
Fix available
A fix is available. Upgrade to after 773 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). This vulnerability allows an attacker to perform cookie hijacking and log in as that user without the need for credentials. This issue affects Pandora FMS: from 700 through 773.

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

This is a stored Cross-site Scripting (XSS) vulnerability in Pandora FMS web application. The vulnerability allows attackers to inject malicious scripts through user input that is improperly sanitized during page generation, enabling cookie hijacking and authentication bypass. The issue affects all versions from 700 through 773.

MitigationApply output encoding/sanitization to all user-supplied input rendered in web pages, implement Content Security Policy headers, and upgrade to version 774 or later which contains the official patch.

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, <= 773

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. Determine Pandora FMS version
    Access the web interface footer or check the /var/www/html/pandora_console/include/config.php file for the version variable, or use the command: cat /etc/pandora/pandora_server.conf | grep version
    Affected if The version number is 700, 701, 702, ... through 773 (any version >= 700 and <= 773)
  2. Verify web console is accessible
    Confirm the Pandora FMS web interface is reachable by accessing the URL (typically http://yourserver/pandora_console) and checking for a login page
    Affected if The web console is exposed and accessible to users or attackers
  3. Identify user input fields in web interface
    Log into the web console and navigate to configuration areas where user-provided data is stored and displayed (such as user profiles, agent descriptions, custom fields, or notification templates)
    Affected if User-controllable input fields exist that accept and render data without visible sanitization indicators
  4. Check database for stored XSS payloads
    Query the Pandora FMS database (typically named pandora) for suspicious script tags in text fields: SELECT * FROM tusr_usuario WHERE fullname LIKE '%<script%' OR comments LIKE '%<script%' (adjust table/column names based on your schema)
    Affected if Records containing HTML script tags, javascript: URLs, or event handler attributes (onerror, onload, etc.) are found in user-related tables

You are affected if Pandora FMS version is between 700 and 773 inclusive and the web interface is accessible, allowing untrusted users to input data that gets stored and rendered without sanitization.

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

Apply output encoding/sanitization to all user-supplied input rendered in web pages, implement Content Security Policy headers, and upgrade to version 774 or later which contains the official patch.

Recommended fix Moderate confidence

Upgrade to Pandora FMS version 774 or later

  1. Identify your current Pandora FMS version by checking the dashboard or using the 'pandora_manage' command line tool
  2. Access the official Pandora FMS download page at pandorafms.com and navigate to the releases section
  3. Download the latest stable release (version 774 or later, as the vulnerability affects versions 700-773)
  4. Before upgrading, backup your database using: mysqldump -u <user> -p pandora > pandora_backup.sql
  5. Before upgrading, backup your configuration files in /etc/pandora/
  6. Follow the official upgrade documentation for your Linux distribution to install the new version
  7. After upgrade, verify the version number matches the fixed release
  8. Clear browser cookies and test that the application functions normally
Caveat Review release notes for any database schema changes or configuration file format updates that may require manual intervention during upgrade

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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