# CVE-2026-34216: CtrlPanel: Authenticated Remote Code Execution via Dynamic Class Instantiation in SettingsController.php

> Authenticated admins can execute arbitrary code by supplying malicious class names to the settings update endpoint in CtrlPanel.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2026
- **Updated:** 20 May 2026
- **Also known as:** GHSA-vcg3-fjrx-rg5q

## What is CVE-2026-34216?

CVE-2026-34216 is a medium-severity code injection vulnerability in Ctrlpanel-gg panel, published on 19 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

CtrlPanel is open-source billing software for hosting providers. In versions 1.1.1 and prior, the admin settings update endpoint accepted a fully qualified class name directly from user-supplied request input and used it for dynamic static method calls and object instantiation without any allowlist validation, allowing for authenticated Remote Code Execution. An authenticated admin-level user could supply an arbitrary class name available in the Composer autoloader, potentially triggering unintended constructor or magic method execution. The update() method reads settings_class directly from the HTTP request and passed it to new $settings_class() and $settings_class::getValidations() without verifying that the provided value corresponds to a legitimate settings class: Because PHP resolves class names against the Composer autoloader at runtime, any autoloadable class in the application or its dependencies could be instantiated. Depending on the classes available in the dependency tree, this can trigger unintended side effects through constructors or magic methods (__construct, __toString, __wakeup), following a PHP object injection / gadget chain pattern. This issue has been fixed in version 1.2.0.

Weakness: CWE-470 (Use of Externally-Controlled Input to Select Classes or Code)

## Which versions are affected by CVE-2026-34216?


## How do I fix CVE-2026-34216?

No fix has been published for CVE-2026-34216 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-34216 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34216 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34216 and fix it if it is affected.

What it is: CVE-2026-34216 is a medium-severity code injection vulnerability in Ctrlpanel-gg panel, published on 19 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34216 exists.

Affected product: Ctrlpanel-gg panel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34216/ (Markdown: https://insights.sbomify.com/CVE-2026-34216/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34216
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34216
- OSV: https://osv.dev/vulnerability/CVE-2026-34216

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34216/
Summaries are generated and may contain mistakes; the official description above is the record.