dbcve.org
Pandora FmsApplication · Artica

CVE-2026-34187

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 777.17 / 802 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 an SQL Command vulnerability allows SQL Injection via graph container parameter. 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

SQL injection vulnerability in Pandora FMS affecting versions 777-800. The flaw exists in the graph container parameter where user-supplied input is improperly neutralized before being used in SQL queries, allowing unauthenticated attackers to inject arbitrary SQL commands.

MitigationUpgrade to a patched version beyond 800. If immediate upgrade is not possible, implement strict input validation on all graph container parameters and use parameterized queries to prevent SQL injection.

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.17>= 778, < 802

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. Identify Pandora FMS installation
    Check for Pandora FMS by looking for the web application in common locations such as /var/www/html/pandora, /opt/pandora, or by identifying the Pandora FMS web server process listening on port 80/443
    Affected if Pandora FMS web application is found and accessible on the system
  2. Determine installed Pandora FMS version
    Check the version file typically located at /var/www/html/pandora/pandora_console/include/config.php or look at the login page footer which displays the version number
    Affected if The displayed version falls within < 777.17 or >= 778 and < 802
  3. Verify graph container feature is accessible
    Check if the web interface is accessible without authentication and if graph container endpoints exist by attempting to access URLs containing 'graph' or 'container' parameters in the Pandora FMS console
    Affected if The graph container parameter is available in the web interface without requiring authentication
  4. Confirm parameter handling exposure
    Review web server access logs for requests to graph-related endpoints with the 'container' parameter to identify if such requests are being processed
    Affected if Requests with the 'container' parameter are being logged and processed by the application

A system is affected if it runs Pandora FMS version 777.x below 777.17, or any version from 778 through 801, and the web interface with graph container functionality is 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 777.17 / 802 or later
Fixed in 777.17802
Interim mitigation

Upgrade to a patched version beyond 800. If immediate upgrade is not possible, implement strict input validation on all graph container parameters and use parameterized queries to prevent SQL injection.

Recommended fix High confidence

Pandora FMS 802 or later

  1. Back up the Pandora FMS database and configuration files before starting the upgrade
  2. Download Pandora FMS version 802 or later from the official source (pandorafms.com)
  3. Stop all Pandora FMS services (pandora_server, tentacle_server, httpd)
  4. Install the new version using the official upgrade procedure for your platform
  5. Verify the SQL injection vulnerability in the graph container parameter is no longer present after upgrade
  6. Restart all Pandora FMS services and confirm normal operation
Caveat Review release notes for version 802 for any configuration or feature changes that may require adjustment

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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