dbcve.org
Pandora FmsApplication · Artica

CVE-2023-41787

HIGH · 7.5 CVSS v3.1 Published 2023-11-23
Fix available
A fix is available. Upgrade to 773 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Uncontrolled Search Path Element vulnerability in Pandora FMS on all allows Leveraging/Manipulating Configuration File Search Paths. This vulnerability allows access to files with sensitive information. This issue affects Pandora FMS: from 700 through 772.

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

Uncontrolled Search Path Element vulnerability in Pandora FMS versions 700-772 allows attackers to manipulate configuration file search paths, potentially causing the application to load malicious configurations or access sensitive files outside intended directories.

MitigationUpdate Pandora FMS to a patched version beyond 772. Additionally, restrict file system permissions and ensure the application runs from a secure, isolated directory to limit path manipulation opportunities.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installed Pandora FMS version
    Access the Pandora FMS web interface and navigate to 'System Information' or 'About' section to view the exact version number. Alternatively, check the version file in the installation directory if command-line access is available.
    Affected if The installed version is 700 or higher but lower than 773.
  2. Locate Pandora FMS configuration directories
    Identify the primary configuration directory where Pandora FMS stores config.php and other configuration files. Common locations include /var/www/html/pandora_console/include or the installation root directory.
    Affected if Configuration directories are world-writable or located in a shared/public directory where other users could place malicious config files.
  3. Verify file permissions on config files
    Check file permissions on configuration files (config.php, pandora_console.conf, etc.) using 'ls -la' command. Verify that only the application user has write access.
    Affected if Configuration files have weak permissions allowing unauthorized modification or are owned by a shared/low-privilege user.
  4. Inspect for unexpected config files in search path
    Review the directories in Pandora FMS's include path by examining the application's configuration loading code or scanning for extra config files in parent/temporary directories.
    Affected if Additional or unexpected configuration files exist in directories the application searches before the intended config location.

You are affected if Pandora FMS version is between 700 and 772 inclusive AND configuration files have weak permissions or can be influenced by unauthorized users in the application's file search path.

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 773 or later
Fixed in 773
Interim mitigation

Update Pandora FMS to a patched version beyond 772. Additionally, restrict file system permissions and ensure the application runs from a secure, isolated directory to limit path manipulation opportunities.

Recommended fix Moderate confidence

773

  1. Download Pandora FMS version 773 or later from the official Pandora FMS repository
  2. Back up the current Pandora FMS installation and database before upgrading
  3. Follow the standard Pandora FMS upgrade procedure for your operating system
  4. Verify the installation after upgrade by checking that the web interface is accessible and all services are running
  5. Confirm the version number post-upgrade matches the fixed release (773 or higher)

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

Fix this in Pandora Fms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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