dbcve.org
Pandora FmsApplication · Artica

CVE-2023-44091

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to 776 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 ('SQL Injection') vulnerability in Pandora FMS on all allows SQL Injection. This ulnerability allowed SQL injections to be made even if authentication failed.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 Pandora FMS affecting versions 700 through <776. The flaw allows unauthenticated attackers to inject arbitrary SQL commands due to improper neutralization of special elements in SQL queries, even when authentication fails.

MitigationUpgrade Pandora FMS to version 776 or later which contains the patch for this SQL injection vulnerability. If immediate upgrade is not possible, implement web application firewall (WAF) rules to block SQL injection payloads as a temporary mitigation.

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
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 version
    Locate the version file or check the web interface footer for the exact version number (usually displayed as 'Pandora FMS X.X.X' in the login page footer or in / Pandora FMS directory structure)
    Affected if Installed version is 700 or higher but lower than 776
  2. Confirm web interface is accessible
    Access the Pandora FMS login URL (typically at /pandora_console/ or /) via HTTP/HTTPS to verify the application is reachable
    Affected if The web interface is exposed and responds to authentication requests
  3. Review web server access logs for SQL injection probes
    Examine web server access logs (Apache/nginx access logs) for unusual SQL syntax in GET/POST parameters targeting the login endpoint, such as: ' OR 1=1, UNION SELECT, or single quotes in authentication fields
    Affected if Logs contain SQL injection payloads in authentication-related request parameters
  4. Check for unauthorized database modifications
    Query the Pandora FMS database (if database access is available) for unexpected user accounts, modified permissions, or suspicious data in the tconfig_extension and tusers tables
    Affected if Unknown administrator accounts exist or database tables show unexpected modifications
  5. Examine failed authentication logs for anomalies
    Review authentication logs for patterns of repeated failed login attempts with SQL injection payloads, especially from a single source IP address
    Affected if Logs show SQL injection patterns in failed authentication attempts

The environment is affected if Pandora FMS version is between 700 and 775 (inclusive) and the web interface is accessible to unauthenticated users.

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 which contains the patch for this SQL injection vulnerability. If immediate upgrade is not possible, implement web application firewall (WAF) rules to block SQL injection payloads as a temporary mitigation.

Recommended fix High confidence

Pandora FMS 776

  1. 1. Back up your current Pandora FMS database and configuration files
  2. 2. Download Pandora FMS version 776 or later from the official source (pandorafms.com)
  3. 3. Follow the official Pandora FMS upgrade documentation for your specific deployment method
  4. 4. After upgrade, verify the SQL injection vulnerability is patched by testing that malformed SQL in login/authentication inputs is properly neutralized
  5. 5. Confirm normal authentication and application functionality still work correctly

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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