dbcve.org
Pandora FmsApplication · Artica

CVE-2026-30804

HIGH · 7.2 CVSS v3.1 Published 2026-04-13
Fix available
A fix is available. Upgrade to 800.1 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
Unrestricted Upload of File with Dangerous Type vulnerability allows Remote Code Execution via file upload. 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

Pandora FMS versions 777 through 800 contain an unrestricted file upload vulnerability that allows remote attackers to upload files with dangerous types (such as executable scripts) to the server, leading to remote code execution.

MitigationRestrict and validate file upload functionality by implementing strict allowlist-based file type validation, storing uploads outside the webroot, disabling script execution in upload directories, and renaming uploaded files.

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
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 version
    Locate the version file or check the web interface footer for the version number. Common locations include / Pandora FMS console/login page, or config files in the installation directory.
    Affected if The installed version is 777, 778, 779, 780, 781, 782, 783, 784, 785, 786, 787, 788, 789, 790, 791, 792, 793, 794, 795, 796, 797, 798, 799, or 800 (any version >= 777 and < 800.1)
  2. Locate file upload functionality
    Access the Pandora FMS web interface and navigate to sections that handle file uploads, typically under Enterprise Manager, Policy Manager, or Incident Management menus. Identify which modules allow file attachments.
    Affected if File upload features are accessible and operational in the web interface
  3. Identify upload storage location
    Inspect the web server configuration and Pandora FMS setup to determine where uploaded files are stored. Check if the uploads directory is within the web document root (htdocs, html, or public_html).
    Affected if Uploaded files are stored in a directory accessible via HTTP/HTTPS (within the webroot)
  4. Verify script execution restrictions
    Check the web server configuration (Apache nginx config) for the upload directory. Look for directives that disable script execution (Options -ExecCGI, RemoveHandler, or equivalent).
    Affected if Script execution is NOT disabled in the upload directory, allowing uploaded PHP, JSP, or CGI files to execute

A user is affected if their Pandora FMS installation version is 777 through 800 (less than 800.1) AND the file upload feature is accessible AND uploads are stored in a web-accessible directory without script execution restrictions.

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

Restrict and validate file upload functionality by implementing strict allowlist-based file type validation, storing uploads outside the webroot, disabling script execution in upload directories, and renaming uploaded files.

Recommended fix High confidence

800.1 or later

  1. 1. Create a complete backup of the current Pandora FMS installation including all configuration files and the database
  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 before performing the upgrade
  4. 4. Follow the official Pandora FMS upgrade documentation for your specific installation type (package-based or source-based)
  5. 5. Apply the new version files, ensuring all components are updated (server, console, and database schema)
  6. 6. Start the Pandora FMS services and verify the application is running
  7. 7. Verify the file upload functionality works correctly and test that malicious file uploads are now blocked
  8. 8. Confirm the version number displays as 800.1 or later in the Pandora FMS interface

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pandora Fms Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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