dbcve.org
Pandora FmsApplication · Artica

CVE-2023-44090

MEDIUM · 6.4 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to 776 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable

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 ('SQL Injection') vulnerability in Pandora FMS on all allows CVE-2008-5817. This vulnerability allowed SQL changes to be made to several files in the Grafana module. This issue affects Pandora FMS: from 700 through <776.

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 the Grafana module of Pandora FMS versions 700 through 775 allows attackers to inject malicious SQL commands, potentially enabling unauthorized database modifications.

MitigationUpgrade Pandora FMS to version 776 or later. Alternatively, implement proper input validation and parameterized queries in the Grafana module files to remediate the 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:>= 700, < 776

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
High
Privileges
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:R/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. Verify Pandora FMS installation
    Locate Pandora FMS installation directories (typically under /var/www/html/pandora, /opt/pandora, or C:\inetpub\wwwroot\pandora on Windows). Check for the presence of pandora_console directory or pandora_server processes.
    Affected if Pandora FMS is not found on the system, the CVE does not apply.
  2. Identify installed Pandora FMS version
    Access the Pandora FMS console login page, or check the version file (usually includes/Version.php or similar version info file in the installation root). Alternatively, check package manager if installed via apt/yum.
    Affected if Installed version is greater than or equal to 700 AND less than 776 - the system falls within the vulnerable range.
  3. Confirm Grafana module is enabled
    Check the Pandora FMS administration panel or configuration files (typically pandora_console/include/config.php or similar) for the Grafana integration module settings. Look for grafana_enabled, grafana_module, or integration settings.
    Affected if The Grafana module is active or integration with Grafana is configured in Pandora FMS.
  4. Inspect Grafana module configuration files
    Review files in the Pandora FMS installation under include/grafana or extension directories related to Grafana. Check for user input parameters in Grafana-related PHP files that could be used in SQL queries without proper sanitization.
    Affected if Grafana module files exist and accept user-supplied input parameters (such as dashboard IDs, panel IDs, or API keys) that may be used in SQL statements.

System is affected if Pandora FMS version 700-775 is installed AND the Grafana module integration is enabled, allowing SQL injection through unsanitized input in Grafana-related functionality.

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

Upgrade Pandora FMS to version 776 or later. Alternatively, implement proper input validation and parameterized queries in the Grafana module files to remediate the SQL injection.

Recommended fix High confidence

Upgrade to Pandora FMS version 776 or later

  1. 1. Back up your current Pandora FMS database and configuration files before proceeding with any upgrade.
  2. 2. Review the official Pandora FMS upgrade documentation for your current version.
  3. 3. Download Pandora FMS version 776 or later from the official Pandora FMS repository (pandorafms.com).
  4. 4. Execute the upgrade process following the standard upgrade procedure for your operating system.
  5. 5. After upgrade, verify the Grafana module functionality is working correctly.
  6. 6. Test that the SQL injection vulnerability is no longer present by reviewing Grafana module configurations.
Caveat Review release notes for version 776 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
  • 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-2023-44090 — 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-2023-44090 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