dbcve.org
Pandora FmsApplication · Artica

CVE-2023-41812

HIGH · 8.8 CVSS v3.1 Published 2023-11-23
Fix available
A fix is available. Upgrade to 774 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Unrestricted Upload of File with Dangerous Type vulnerability in Pandora FMS on all allows Accessing Functionality Not Properly Constrained by ACLs. This vulnerability allowed PHP executable files to be uploaded through the file manager. 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

Pandora FMS versions 700-773 contain an unrestricted file upload vulnerability in the file manager component. The application fails to properly constrain file uploads, allowing attackers to upload executable PHP files that can be accessed and executed server-side, leading to remote code execution.

MitigationRestrict the file manager to accept only safe, non-executable file types (images, documents); implement proper ACL enforcement and server-side file type validation; move uploaded files outside web-accessible directories.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 administration console and navigate to the 'About' or 'System Information' section, typically found under 'Setup' > 'System' or by clicking the user profile. Alternatively, check the file 'general/pandora_console/include/config.php' for a version constant, or execute: grep -r 'CURRENT_VERSION' /path/to/pandora/console/include/
    Affected if The installed version is greater than or equal to 700 but less than 774
  2. Verify file manager component is accessible
    Log in to the Pandora FMS web console as an administrative user. Navigate to 'File Manager' in the main menu, typically under 'Resources' or 'Extensions'. Confirm the component loads without access denied errors.
    Affected if The file manager interface is accessible and functional
  3. Check file upload functionality status
    Within the file manager component, attempt to identify if file upload features are enabled. Look for an 'Upload' button or file attachment interface in the file manager view. Check user permissions for the logged-in account.
    Affected if File upload functionality is enabled and available to the current user role
  4. Inspect web server configuration for uploaded files
    Locate the directory where uploaded files are stored. This is typically under the Pandora FMS web root (e.g.,/pandora_console/attachment/ or similar). Verify if these files are served from a web-accessible path.
    Affected if Uploaded files are stored in a web-accessible directory and can be accessed via HTTP

A user is affected if their Pandora FMS installation is version 700 through 773 and the file manager with upload capability is accessible to their user account.

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

Restrict the file manager to accept only safe, non-executable file types (images, documents); implement proper ACL enforcement and server-side file type validation; move uploaded files outside web-accessible directories.

Recommended fix High confidence

Pandora FMS 774 or later

  1. 1. Back up the current Pandora FMS installation and database before proceeding with the upgrade.
  2. 2. Download Pandora FMS version 774 or later from the official Pandora FMS distribution channels (pandorafms.com).
  3. 3. Follow the official Pandora FMS upgrade documentation to install version 774 or later, replacing the affected installation.
  4. 4. Verify that PHP executable files can no longer be uploaded through the file manager (this vulnerability vector should be blocked).
  5. 5. Confirm that legitimate file upload functionality continues to work as expected.

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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