dbcve.org
Pandora FmsApplication · Pandorafms

CVE-2022-1648

HIGH · 7.2 CVSS v3.1 Published 2022-07-26
Fix available
A fix is available. Upgrade to after 7.0_ng_760 or later.
See remediation →
78/100
Remediation priority · High
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
Pandora FMS v7.0NG.760 and below allows a relative path traversal in File Manager where a privileged user could upload a .php file outside the intended images directory which is restricted to execute the .php file. The impact could lead to a Remote Code Execution with running application privilege.

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 relative path traversal vulnerability in the File Manager component of Pandora FMS v7.0NG.760 and below allows a privileged user to upload a .php file outside the intended images directory, bypassing directory restrictions. The uploaded file can then be executed, leading to Remote Code Execution with the application's privileges.

MitigationUpgrade to a patched version of Pandora FMS. Additionally, implement strict path validation to ensure uploaded files remain within allowed directories and disable PHP execution in upload 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:<= 7.0_ng_760

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

CVSS:3.1/AV:N/AC:L/PR:H/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 Pandora FMS installation and version
    Locate the Pandora FMS installation directory and check the version file or dashboard for the installed version number (typically found in include/config.php or displayed in the web UI footer)
    Affected if The installed version is 7.0NG.760 or lower (any version up to and including 7.0_ng_760)
  2. Confirm File Manager component is accessible
    Verify that the File Manager feature is enabled and accessible within the Pandora FMS administrative interface. Check if the endpoint /general/file_manager or similar is reachable
    Affected if The File Manager component is enabled and accessible to privileged users in the environment
  3. Verify PHP execution restrictions in upload directories
    Inspect the web server configuration (Apache/Nginx) and the upload directories (typically under /images or /uploads within the Pandora FMS web root) to determine if PHP execution is allowed in these directories
    Affected if PHP execution is permitted in directories where file uploads are stored, allowing uploaded PHP files to be executed
  4. Check for unexpected PHP files in non-image directories
    Scan the Pandora FMS web directory tree for .php files located outside the expected application directories, particularly in areas reachable via HTTP/HTTPS
    Affected if Any .php files are found in directories outside the intended application structure, especially in upload/image directories

A user is affected if they are running Pandora FMS version 7.0NG.760 or lower, have the File Manager enabled, and do not have PHP execution disabled in upload directories.

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 7.0_ng_760
Interim mitigation

Upgrade to a patched version of Pandora FMS. Additionally, implement strict path validation to ensure uploaded files remain within allowed directories and disable PHP execution in upload directories.

Recommended fix Moderate confidence

Fixed release after 7.0NG.760 (specific version number not provided in reference material)

  1. 1. Identify all Pandora FMS instances running version 7.0NG.760 or below
  2. 2. Check vendor release notes (pandorafms.com or www.incibe.es) for the security release containing the fix for CVE-2022-1648
  3. 3. Download the fixed version from the official Pandora FMS download repository
  4. 4. Backup the current Pandora FMS installation including database and configuration files
  5. 5. Test the upgrade in a non-production environment first
  6. 6. Apply the upgrade following the official upgrade documentation
  7. 7. Verify the File Manager functionality works correctly post-upgrade
  8. 8. Confirm the patch is applied by checking the version number and reviewing /var/www/html/pandora_console/ (or equivalent install path) for any file manager security changes
Caveat Review upgrade documentation for potential breaking changes between 7.0NG.760 and the target fixed version, particularly any database schema changes

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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