dbcve.org
Pandora FmsApplication · Artica

CVE-2023-44092

CRITICAL · 9.1 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to 776 or later.
See remediation →
97/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
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Pandora FMS on all allows OS Command Injection. This vulnerability allowed to create a reverse shell and execute commands in the OS. This issue affects Pandora FMS: from 700 through <776.

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

OS Command Injection vulnerability in Pandora FMS affecting versions 700 through 776. Attackers can inject and execute arbitrary OS commands, potentially creating reverse shells and achieving full system compromise. The critical CVSS 9.1 indicates network-exploitable with no authentication required.

MitigationUpgrade Pandora FMS to version 776 or later. If immediate patching is not feasible, restrict network access to the Pandora FMS interface and deploy input validation or WAF rules to block malicious command payloads.

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

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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
    Identify where Pandora FMS is installed. Common locations include /var/www/html/pandora on Linux systems, or check the web server document root. Look for the pandora_console directory which contains the web interface.
    Affected if Installation directory cannot be found or is inaccessible for version checking
  2. Determine installed Pandora FMS version
    Check the version file typically found in the pandora_console/include/config.php file, or look for a version.php file in the include directory. Alternatively, access the Pandora FMS login page and check the footer for the version number, or examine the output of the pandora_server command with --version if available.
    Affected if Version cannot be determined from configuration files or web interface
  3. Compare version against vulnerable range
    Verify if the installed version is greater than or equal to 700 AND less than 776. The vulnerable range is versions 700 through 775.x. Version 776 and later are patched.
    Affected if Installed version is >= 700 and < 776 (for example, 700, 720, 750, 775.5, etc.)
  4. Assess network exposure of web interface
    Determine if the Pandora FMS web console (pandora_console) is accessible from untrusted networks. Check firewall rules, reverse proxy configurations, and network ACLs that govern access to port 80/443 where Pandora FMS is hosted.
    Affected if Web interface is exposed to the internet or untrusted internal networks without authentication barriers

The environment is affected if Pandora FMS version is 700 or higher but below 776, and the web interface is network-accessible.

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

Upgrade Pandora FMS to version 776 or later. If immediate patching is not feasible, restrict network access to the Pandora FMS interface and deploy input validation or WAF rules to block malicious command payloads.

Recommended fix High confidence

776 or later

  1. 1. Create a complete backup of the Pandora FMS database and configuration files before proceeding
  2. 2. Download Pandora FMS version 776 or later from the official Pandora FMS repository (e.g., https://pandorafms.com/downloads/)
  3. 3. Review the official Pandora FMS upgrade documentation for your specific installation method (standalone, docker, or package-based)
  4. 4. Stop the Pandora FMS services to ensure data integrity during upgrade
  5. 5. Install the new version following the documented upgrade procedure for your deployment type
  6. 6. Start the Pandora FMS services after successful installation
  7. 7. Verify the installation by logging into the web interface and checking that all components function correctly
  8. 8. Confirm the version number displays as 776 or higher in the Pandora FMS console
Caveat Review release notes for version 776+ to check for any configuration or feature changes that may require adjustment during upgrade

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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