dbcve.org
Pandora FmsApplication · Artica

CVE-2026-30809

HIGH · 8.8 CVSS v3.1 Published 2026-04-13
Fix available
A fix is available. Upgrade to 800.1 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
Improper Neutralization of Special Elements used in an OS Command vulnerability allows OS Command Injection via WebServerModuleDebug. This issue affects Pandora FMS: from 777 through 800

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 WebServerModuleDebug allows attackers to execute arbitrary operating system commands through unsanitized input. The vulnerability affects versions 777 through 800 and stems from improper neutralization of special elements when constructing OS commands.

MitigationUpgrade Pandora FMS to a version beyond 800 that includes the patch, or disable the WebServerModuleDebug module if not needed. If immediate patching is not possible, restrict network access to debug endpoints 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:>= 777, < 800.1

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. Confirm Pandora FMS installation
    Check for Pandora FMS installation by looking for the product's web files, processes, or installation directories typical of this application (often in /var/www/html, /opt, or similar web root locations). Look for pandora processes running or pandora-related web content.
    Affected if Pandora FMS is not installed on the system
  2. Identify installed Pandora FMS version
    Access the Pandora FMS web interface and navigate to the admin or about section to view the version number, or check version files in the installation directory if accessible.
    Affected if The installed version falls within >=777 and <800.1
  3. Locate WebServerModuleDebug component
    Search the Pandora FMS installation for files or components named WebServerModuleDebug, ModuleDebug, or similar debug-related modules in the web application structure.
    Affected if The WebServerModuleDebug component exists in the installation
  4. Verify debug module is enabled
    Check the configuration files or admin settings to determine if the debug module is currently enabled and accessible via the web interface.
    Affected if The debug module is enabled and accessible without additional authentication barriers beyond standard login

A user is affected if Pandora FMS version is >=777 and <800.1, the WebServerModuleDebug component exists, and that debug module is enabled in their environment.

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

Upgrade Pandora FMS to a version beyond 800 that includes the patch, or disable the WebServerModuleDebug module if not needed. If immediate patching is not possible, restrict network access to debug endpoints and implement web application firewall rules to detect and block command injection attempts.

Recommended fix High confidence

Pandora FMS 800.1 or later

  1. 1. Back up the current Pandora FMS installation and database before upgrading
  2. 2. Download Pandora FMS version 800.1 or later from the official Pandora FMS download repository (pandorafms.com)
  3. 3. Stop the Pandora FMS services (Pandora Server, Pandora DB, and web server)
  4. 4. Upgrade the Pandora FMS installation following the official upgrade documentation for your operating system
  5. 5. Verify that WebServerModuleDebug is not exposed in production environments - this parameter should be disabled in production
  6. 6. Start the Pandora FMS services
  7. 7. Verify the upgrade was successful by logging into the web interface and checking the version information
  8. 8. Test that critical functionality works as expected
Caveat Review the release notes for 800.1 for any specific migration steps or configuration changes from your current version

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-2026-30809 — 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-2026-30809 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