Skip to content
Heist/ feed
Back to feed
Medium

CtrlPanel: Authenticated Remote Code Execution via Dynamic Class Instantiation in SettingsController.php

Type: advisorySources: OSV

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.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2026-34216
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 04:22 UTC · Revision 1

Source evidence

CtrlPanel: Authenticated Remote Code Execution via Dynamic Class Instantiation in SettingsController.php

core-osv · Original source

Published 19 May 2026, 20:31 UTC

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.

osv:CVE-2026-34216
Complete source record
{
  "id": "3b061fd9bb66aaa749fd12dce6f0fa4810a390d414116e6e554f439192b2c405",
  "url": "https://osv.dev/vulnerability/CVE-2026-34216",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "CtrlPanel: Authenticated Remote Code Execution via Dynamic Class Instantiation in SettingsController.php",
    "summary": "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.",
    "evidence": "osv:CVE-2026-34216",
    "products": [],
    "severity": "medium",
    "structured": {
      "id": "CVE-2026-34216",
      "aliases": [
        "CVE-2026-34216",
        "GHSA-vcg3-fjrx-rg5q"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/ctrlpanel-gg/panel",
              "type": "GIT",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "b3bd1ed50b9f50b76797d09609980fdb4ae70252"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "range": [
                      {
                        "introduced": "0"
                      },
                      {
                        "fixed": "1.2.0"
                      }
                    ],
                    "source": "AFFECTED_FIELD",
                    "strategy": "StringRangeExpression"
                  },
                  {
                    "range": [
                      {
                        "fixed": "b3bd1ed50b9f50b76797d09609980fdb4ae70252"
                      }
                    ],
                    "source": "REFERENCES_TAG",
                    "original_tag": "1.2.0"
                  }
                ]
              }
            }
          ],
          "versions": [
            "1.1.1",
            "1.1",
            "1.0.8",
            "1.0.7",
            "1.0.6",
            "1.0.5",
            "1.0.4",
            "1.0.3",
            "1.0.2",
            "1.0.1",
            "1.0",
            "0.1"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-34216.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:25.687637319Z",
      "provider": "osv",
      "references": [
        "https://github.com/Ctrlpanel-gg/panel/releases/tag/1.2.0",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/34xxx/CVE-2026-34216.json",
        "https://github.com/Ctrlpanel-gg/panel/security/advisories/GHSA-vcg3-fjrx-rg5q",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-34216"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-470"
        ],
        "cna_assigner": "GitHub_M",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/34xxx/CVE-2026-34216.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-34216",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 492435,
  "published_at": "2026-05-19T20:31:16.162+00:00"
}