dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-34234

CRITICAL · 10.0 CVSS v3.1 Published 2026-05-19
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
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
CtrlPanel is open-source billing software for hosting providers. In versions 1.1.1 and prior, the web-based installer (public/installer/index.php) is vulnerable to unauthenticated Remote Code Execution (RCE) because it performs the install.lock check only after including and executing form handler files, leaving installer endpoints reachable on already-installed instances. The handlers also pass unsanitized user input directly into shell commands, allowing an attacker to submit crafted requests that execute arbitrary commands on the server. The vulnerability stems from two combined weaknesses: (1) premature form handler execution before the lock file gate, and (2) unsafe use of user input in shell command construction. This issue is reported to be actively exploited in the wild. The issue has been fixed in version 1.2.0.

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

CtrlPanel versions 1.1.1 and prior contain an unauthenticated RCE vulnerability in the web-based installer (public/installer/index.php). The install.lock check is performed after form handler files are included and executed, leaving installer endpoints accessible on production instances. The handlers pass unsanitized user input directly into shell commands, enabling arbitrary command execution. This is actively exploited in the wild.

MitigationImmediately update to version 1.2.0 and remove or disable the installer directory. Conduct a forensic investigation to check for existing compromise given active exploitation, as the fix alone may not remediate an already compromised system.

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
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 if the installer directory exists
    Check for the presence of the public/installer/ directory on the web server filesystem. Use file system commands like 'ls -la' or file manager tools to enumerate this path.
    Affected if The public/installer/ directory exists on the system, indicating the installer has not been removed after installation.
  2. Check for install.lock file
    Inspect whether the install.lock file exists within the public/installer/ directory. This file should be created after successful installation to block further installer access.
    Affected if The install.lock file is missing, or exists but the installer remains accessible due to the lock check occurring after handler execution.
  3. Determine installed CtrlPanel version
    Locate and read the version file or configuration within the CtrlPanel installation. Common locations include a version.php file, composer.json, or the control panel's about/admin page.
    Affected if The installed version is prior to 1.2.0, as versions before this release contain the vulnerable installer code.
  4. Test installer endpoint accessibility
    Attempt to access the installer URL endpoint (public/installer/index.php) via HTTP request from an external or untrusted network location.
    Affected if The installer page loads or responds, indicating the endpoint is accessible and the install.lock check is not being enforced before handler execution.
  5. Examine handler file code integrity
    Review the form handler files included by the installer (such as those in public/installer/handlers/ or similar paths) for direct usage of user input in shell execution functions like exec(), shell_exec(), or system().
    Affected if Handler files pass $_POST, $_GET, or $_REQUEST parameters directly into shell command functions without sanitization.

A system is affected if CtrlPanel versions prior to 1.2.0 are installed with the public/installer/ directory still present and accessible, regardless of install.lock presence.

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

Immediately update to version 1.2.0 and remove or disable the installer directory. Conduct a forensic investigation to check for existing compromise given active exploitation, as the fix alone may not remediate an already compromised system.

Recommended fix High confidence

CtrlPanel version 1.2.0

  1. 1. Backup the entire CtrlPanel installation including database and configuration files before making any changes.
  2. 2. Download CtrlPanel version 1.2.0 from the official repository or source.
  3. 3. Replace all files in the existing installation with the files from version 1.2.0, preserving configuration files and the database connection details.
  4. 4. Verify that the public/installer/ directory has been removed or is no longer accessible in production environments.
  5. 5. Confirm the install.lock file exists in the installation directory.
  6. 6. Test that the application functions normally after the upgrade.
  7. 7. Monitor logs for any suspicious activity, as this vulnerability is reported as actively exploited.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $2,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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