dbcve.org
Pandora FmsApplication · Artica

CVE-2026-34186

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 SQL Command vulnerability allows SQL Injection via custom fields. 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

SQL injection vulnerability in Pandora FMS custom fields (versions 777-800) allows attackers to inject malicious SQL commands through unsanitized input in custom field parameters. The high CVSS score of 8.8 indicates significant risk to data confidentiality and integrity.

MitigationApply vendor patch immediately or upgrade to a fixed version. Until then, implement input validation on custom field endpoints and enforce least-privilege database accounts to limit injection impact.

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. Identify installed Pandora FMS version
    Access the Pandora FMS administration console and navigate to 'Setup' > 'General' > 'About' to view the installed version number, or query the system directly via command line if you have server access
    Affected if The installed version is 777 or higher but below 800.1
  2. Verify custom fields are configured
    In the Pandora FMS console, go to 'Manage Agents' > 'Custom Fields' to see if any custom fields have been created for agents or modules
    Affected if Custom fields exist in the system, as the SQL injection only affects this feature
  3. Check custom field data handling
    Review the database tables related to custom fields (typically table prefix followed by tcustom_field or similar) to identify any injected SQL payloads in field values, or examine HTTP requests to custom field endpoints for suspicious input patterns
    Affected if Malicious SQL syntax is found in custom field value records in the database
  4. Inspect web server logs for SQL injection attempts
    Review web server access logs (Apache/Nginx) for requests to custom field handling endpoints (such as ajax.php or included PHP files) containing SQL operators like UNION, SELECT, or comment characters in parameter values
    Affected if Suspicious SQL injection patterns are observed in recent web logs targeting custom field functionality

You are affected if running Pandora FMS version 777 through 800 (exclusive of 800.1) and using the custom fields feature, as the SQL injection only applies under these specific conditions.

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

Apply vendor patch immediately or upgrade to a fixed version. Until then, implement input validation on custom field endpoints and enforce least-privilege database accounts to limit injection impact.

Recommended fix Moderate confidence

800.1

  1. 1. Create a full backup of the Pandora FMS database and configuration files
  2. 2. Review the official Pandora FMS upgrade documentation for version 800.1
  3. 3. Download Pandora FMS version 800.1 or later from the official source (pandorafms.com)
  4. 4. Execute the upgrade procedure according to the official documentation
  5. 5. Verify the installation by logging into the console
  6. 6. Test that custom fields functionality works correctly
  7. 7. Confirm the SQL injection vulnerability is resolved by verifying the fix is applied
Caveat Standard upgrade risks apply - review release notes for any configuration or feature changes between your version and 800.1

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
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,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 $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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