dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2014-125115

CRITICAL · 10.0 CVSS v4.0 Published 2025-07-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
An unauthenticated SQL injection vulnerability exists in Pandora FMS version 5.0 SP2 and earlier. The mobile/index.php endpoint fails to properly sanitize user input in the loginhash_data parameter, allowing attackers to extract administrator credentials or active session tokens via crafted requests. This occurs because input is directly concatenated into an SQL query without adequate validation, enabling SQL injection. After authentication is bypassed, a second vulnerability in the File Manager component permits arbitrary PHP file uploads. The file upload functionality does not enforce MIME-type or file extension restrictions, allowing authenticated users to upload web shells into a publicly accessible directory and achieve remote code execution.

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

Pandora FMS 5.0 SP2 and earlier contains an unauthenticated SQL injection in mobile/index.php via the loginhash_data parameter, allowing attackers to extract credentials or session tokens by injecting malicious SQL queries. Following successful authentication bypass, the File Manager component permits unrestricted PHP file uploads without MIME-type or extension validation, enabling remote code execution via web shell deployment.

MitigationReplace direct SQL concatenation with parameterized queries or prepared statements in mobile/index.php to remediate the SQL injection, and implement strict MIME-type validation, allowlist-based extension filtering, and store uploads outside the web root to prevent arbitrary PHP execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 and version
    Locate Pandora FMS installation directory and check version files (typically in main install path, look for version.php or similar version metadata files)
    Affected if Version is 5.0 SP2 or earlier (5.0, 5.0 SP1, 5.0 SP2)
  2. Verify mobile/index.php exists
    Check for the presence of mobile/index.php in the web root or Pandora FMS web directory
    Affected if The mobile/index.php file exists in the deployed application
  3. Confirm loginhash_data parameter usage
    Inspect mobile/index.php source code and search for 'loginhash_data' parameter handling
    Affected if The loginhash_data parameter is used in the mobile/index.php without parameterized queries or input sanitization
  4. Locate File Manager component
    Search for File Manager functionality in Pandora FMS (typically under 'godmode' or 'operation' directories, look for file manager or file upload related modules)
    Affected if File Manager component is present and accessible after authentication bypass
  5. Check upload function validation
    Examine the File Manager upload code for MIME-type validation, extension allowlisting, and upload directory configuration
    Affected if Upload function lacks MIME-type validation, extension filtering, or stores files within the web root enabling PHP execution

A user is affected if running Pandora FMS version 5.0 SP2 or earlier with mobile/index.php accessible and the loginhash_data parameter vulnerable to SQL injection, followed by access to an unrestricted File Manager upload feature.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace direct SQL concatenation with parameterized queries or prepared statements in mobile/index.php to remediate the SQL injection, and implement strict MIME-type validation, allowlist-based extension filtering, and store uploads outside the web root to prevent arbitrary PHP execution.

Recommended fix Moderate confidence

Latest stable Pandora FMS release (version greater than 5.0 SP2)

  1. 1. Backup the current Pandora FMS installation and database before making any changes.
  2. 2. Download the latest stable version of Pandora FMS from the official vendor website or repository.
  3. 3. Upgrade the Pandora FMS installation to the latest version to resolve both the SQL injection and arbitrary file upload vulnerabilities.
  4. 4. After upgrading, verify that the mobile/index.php endpoint properly sanitizes the loginhash_data parameter.
  5. 5. Confirm that the File Manager component now enforces proper MIME-type and file extension restrictions to prevent PHP uploads.
  6. 6. Test that the authentication mechanism is working correctly and SQL injection is no longer possible.
  7. 7. Validate that file upload functionality restricts allowed file types to non-executable formats.
  8. 8. Review all administrative accounts and reset credentials as a precaution, since the SQL injection could have exposed password hashes.
Caveat Major version upgrades may introduce changes to configuration files, plugins, or custom integrations; review upgrade documentation thoroughly before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed 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 help mitigating

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-2014-125115 — 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-2014-125115 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