dbcve.org
Pandora FmsApplication · Artica

CVE-2026-30811

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-13
Fix available
A fix is available. Upgrade to 800.1 or later.
See remediation →
71/100
Remediation priority · Elevated
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
Missing Authorization vulnerability allows Exposure of Sensitive Information via configuration endpoint. 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 · moderate confidence

Pandora FMS versions 777-800 contain a missing authorization check on a configuration endpoint, allowing unauthenticated or unauthorized users to access sensitive configuration data through this endpoint.

MitigationImplement proper authorization checks on the configuration endpoint to ensure only authenticated users with appropriate permissions can access sensitive configuration information.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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
    Locate Pandora FMS in your environment by checking for the pandora service, common installation directories such as /var/www/html/pandora_console, or by querying running processes for pandora-related binaries.
    Affected if Pandora FMS software is present on the system
  2. Determine installed version
    Access the Pandora FMS web console login page and examine the footer, or check the version file in the installation directory if accessible, or run: grep -r 'version' /var/www/html/pandora_console 2>/dev/null | head -20
    Affected if The installed version falls within the range 777 to 800 (inclusive of 777, exclusive of 800.1)
  3. Identify configuration endpoint
    Review web server access logs or application documentation for endpoints under paths like /general/setup, /configuration, or /config, or use a web vulnerability scanner to enumerate exposed endpoints.
    Affected if A configuration endpoint exists and is accessible via HTTP/HTTPS
  4. Test unauthenticated access to configuration endpoint
    Using curl or a browser, send a direct request to the suspected configuration endpoint without providing any session cookie, authentication token, or login credentials. Example: curl -k http://TARGET_HOST/pandora_console/index.php?sec=general&sec2=godmode/setup/setup
    Affected if The endpoint returns sensitive configuration data, user credentials, database connection strings, API keys, or system settings without requiring authentication

Your environment is affected if Pandora FMS versions 777 through 800 are installed and the configuration endpoint responds with sensitive data when accessed without authentication credentials.

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

Implement proper authorization checks on the configuration endpoint to ensure only authenticated users with appropriate permissions can access sensitive configuration information.

Recommended fix Moderate confidence

Upgrade to Pandora FMS 800.1 or later

  1. 1. Backup the current Pandora FMS database and configuration files before proceeding with any upgrade.
  2. 2. Verify the current installed version is >= 777 and < 800.1 using the Pandora FMS version check command or web interface.
  3. 3. Download Pandora FMS version 800.1 or later from the official Pandora FMS repository or vendor website.
  4. 4. Stop the Pandora FMS services (pandora_server, tentacle_server, and web server).
  5. 5. Follow the official upgrade documentation for your installation method (manual, package manager, or Docker).
  6. 6. Upgrade the database schema if required by the upgrade process.
  7. 7. Start the Pandora FMS services and verify they are running correctly.
  8. 8. Confirm the new version is 800.1 or higher and the configuration endpoint is now properly protected.
Caveat Review release notes for 800.x for any configuration or feature changes that may affect your setup

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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