dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2014-125123

CRITICAL · 10.0 CVSS v4.0 Published 2025-07-31
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 the Kloxo web hosting control panel (developed by LXCenter) prior to version 6.1.12. The flaw resides in the login-name parameter passed to lbin/webcommand.php, which fails to properly sanitize input, allowing an attacker to extract the administrator’s password from the backend database. After recovering valid credentials, the attacker can authenticate to the Kloxo control panel and leverage the Command Center feature (display.php) to execute arbitrary operating system commands as root on the underlying host system. This vulnerability was reported to be exploited in the wild in January 2014.

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

Unauthenticated SQL injection in Kloxo web hosting control panel's lbin/webcommand.php allows extraction of administrator credentials via the login-name parameter. Successful exploitation enables arbitrary root command execution through the Command Center feature (display.php).

MitigationUpgrade Kloxo to version 6.1.12 or later to patch the SQL injection vulnerability. If immediate patching is not possible, restrict network access to the Kloxo administration interface.

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. Confirm Kloxo installation
    Identify if the Kloxo control panel is installed on the system. This is typically found on Linux servers used for web hosting. Check for Kloxo-related directories or services.
    Affected if Kloxo is installed and the version is prior to 6.1.12.
  2. Determine Kloxo version
    Locate the installed Kloxo version. Common locations include the Kloxo admin interface version display, or check version files in the Kloxo installation directory. Compare your installed version against the affected range of versions prior to 6.1.12.
    Affected if The installed Kloxo version is below 6.1.12.
  3. Verify vulnerable file accessibility
    Check for the presence and accessibility of lbin/webcommand.php in the Kloxo web root. This file handles web commands and accepts the login-name parameter.
    Affected if The file lbin/webcommand.php exists and is accessible without authentication.
  4. Check Command Center feature status
    Determine if the Command Center feature is enabled. This feature is accessed via display.php and allows authenticated users to execute root-level commands.
    Affected if The Command Center feature (display.php) is enabled and accessible.

A system is affected if it runs any Kloxo version prior to 6.1.12 with the lbin/webcommand.php file accessible and the Command Center feature enabled.

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

Upgrade Kloxo to version 6.1.12 or later to patch the SQL injection vulnerability. If immediate patching is not possible, restrict network access to the Kloxo administration interface.

Recommended fix High confidence

Kloxo version 6.1.12 or later

  1. Back up the current Kloxo installation and database before proceeding with any changes
  2. Upgrade Kloxo control panel to version 6.1.12 or later (the fixed release)
  3. After upgrade, change the administrator password immediately to a strong, unique password
  4. Verify the upgrade was successful by checking the version in the Kloxo admin panel
  5. Review system logs for any signs of unauthorized access or compromise that may have occurred prior to patching
  6. If compromise is suspected, consider a full system audit and potential reinstall

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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