dbcve.org
Pandora FmsApplication · Artica

CVE-2024-12992

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-17
Fix available
A fix is available. Upgrade to 777.8 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in a Command vulnerability allows OS Command Injection via RCE. This issue affects Pandora FMS from 700 to 777.6 .

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 critical OS command injection vulnerability in Pandora FMS versions 700 through 777.6. The vulnerability allows remote attackers to execute arbitrary operating system commands due to improper neutralization of special elements in user input, leading to complete system compromise.

MitigationUpgrade to a patched version of Pandora FMS beyond 777.6, or apply vendor-provided patches. If immediate patching is not possible, restrict network access to the Pandora FMS interface and implement Web Application Firewall rules to detect and block command injection attempts.

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, < 777.8

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate Pandora FMS installation
    Look for Pandora FMS directories (commonly in /var/www/html/pandora, /var/www/pandora, or C:\inetpub\wwwroot\pandora) or check running web services for Pandora FMS process.
    Affected if Pandora FMS is found installed on the system.
  2. Identify installed Pandora FMS version
    Check the version file in the Pandora FMS directory. Common locations include: /var/www/html/pandora/pandora_console/include/config.php (look for $config['version'] or similar), or /var/www/pandora_fms/pandora_console/VERSION file, or the about page at /pandora_console/index.php?sec=about.
    Affected if Unable to determine version or version file not found.
  3. Compare version to vulnerable range
    If version is determined, verify if it falls within >= 700 AND < 777.8. For example, versions 700, 750, 777.0, 777.5, 777.6 are all affected. Versions below 700 or 777.8 and above are not affected.
    Affected if Installed version is 700 or higher but lower than 777.8.
  4. Check web interface accessibility
    Verify if the Pandora FMS web console is accessible over network. Test connectivity to the pandora_console path (e.g., http://your-server/pandora_console or https://your-server/pandora_console).
    Affected if Web interface is accessible remotely and version is in the affected range.

The system is affected if Pandora FMS is installed with a version between 700 and 777.6 (or < 777.8) and its web interface is network-accessible, allowing remote attackers to inject OS commands through user input fields.

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

Upgrade to a patched version of Pandora FMS beyond 777.6, or apply vendor-provided patches. If immediate patching is not possible, restrict network access to the Pandora FMS interface and implement Web Application Firewall rules to detect and block command injection attempts.

Recommended fix High confidence

Pandora FMS 777.8 or later

  1. 1. Back up the entire Pandora FMS installation directory and database before proceeding with any upgrade.
  2. 2. Review the official Pandora FMS upgrade documentation for your current version at pandorafms.com.
  3. 3. Download Pandora FMS version 777.8 or later from the official Pandora FMS downloads page.
  4. 4. Stop the Pandora FMS services (pandora_server and tentacle_server).
  5. 5. Follow the official upgrade procedure: extract the new package, run the upgrade script, and ensure all database migrations complete successfully.
  6. 6. Verify the upgrade by checking the Pandora FMS version in the web interface under 'Administration' > 'Manage Servers' or by running the version check command.
  7. 7. Restart the Pandora FMS services and confirm all components are functioning properly.
  8. 8. Validate that the command injection vulnerability is no longer present by reviewing the system's command execution logs.
Caveat Review the release notes for 777.8+ for any configuration or feature changes that may require adjustments in your environment

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-2024-12992 — 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-2024-12992 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