CVE-2024-51567: CyberPanel: pre-auth RCE via secMiddleware bypass
CRITICAL ACTIVELY EXPLOITED PoC AVAILABLE NUCLEI TEMPLATE CISA: ACTCyberPanel, a widely deployed web hosting control panel, has a pre-authentication remote code execution flaw where the /dataBases/upgrademysqlstatus endpoint bypasses its security middleware — which only validates POST requests — and passes the statusfile parameter unsanitized into a shell command. This is a maximum-severity issue (CVSS 10) sitting in CISA's KEV catalog with an ACT SSVC decision and an EPSS score in the top 0.03% percentile for exploitation likelihood, and it has already been mass-exploited: the PSAUX ransomware campaign hit an estimated 22,000 CyberPanel instances in October 2024. A public PoC and a Nuclei scanning template exist, so unpatched internet-facing instances get found and compromised automatically, not by targeted actors. CyberPanel itself is general server-management software rather than an AI framework, but it is commonly used to host self-managed application stacks — including self-hosted AI/ML workloads such as inference servers, model dashboards, or RAG backends — so a compromised panel hands an attacker root-level control over anything colocated on that box, including model weights, API keys, and database credentials. Patch immediately to the fixed commit (5b08cd6 or later — verify your CyberPanel release actually ships the fix, since 2.3.7 was still unpatched at disclosure), and until patched, block or restrict access to /dataBases/upgrademysqlstatus and watch for anomalous outbound traffic or mass file encryption consistent with PSAUX IOCs.
What is the risk?
Maximum severity (CVSS 10, AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H). Network-reachable, no authentication or user interaction required, low attack complexity, and full confidentiality/integrity/availability impact via arbitrary command execution. Confirmed in CISA KEV with an ACT decision, EPSS in the top 0.03% (0.865 raw score), a public PoC, and a Nuclei template — the combination of trivial exploitability and confirmed mass exploitation (PSAUX ransomware, ~22,000 instances) puts this in the highest-urgency tier for any exposed instance, patched or not yet verified.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| n/a | — | — | No patch |
Do you use n/a? You're affected.
How severe is it?
What is the attack surface?
What should I do?
1 step-
1) Patch to the fixed commit 5b08cd6 or later immediately; confirm your installed version actually includes the fix (2.3.7 was still unpatched at time of disclosure per the advisory). 2) If immediate patching isn't possible, block or firewall access to /dataBases/upgrademysqlstatus and any non-POST access to secMiddleware-protected routes. 3) Deploy a WAF/reverse-proxy rule to strip or reject shell metacharacters in the statusfile parameter. 4) Scan your own perimeter with the public Nuclei template to confirm exposure before an attacker does. 5) Hunt for PSAUX ransomware IOCs (unexpected encrypted files, ransom notes, unusual cron/systemd persistence) on any CyberPanel host. 6) Network-segment CyberPanel-managed hosts away from AI/ML secrets stores (model registries, vector DBs, inference API keys) so a panel compromise doesn't cascade. 7) Since CISA KEV due date (2024-11-28) has passed, treat any still-unpatched instance as a compliance gap for federal/regulated environments.
What does CISA's SSVC say?
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2024-51567?
CyberPanel, a widely deployed web hosting control panel, has a pre-authentication remote code execution flaw where the /dataBases/upgrademysqlstatus endpoint bypasses its security middleware — which only validates POST requests — and passes the statusfile parameter unsanitized into a shell command. This is a maximum-severity issue (CVSS 10) sitting in CISA's KEV catalog with an ACT SSVC decision and an EPSS score in the top 0.03% percentile for exploitation likelihood, and it has already been mass-exploited: the PSAUX ransomware campaign hit an estimated 22,000 CyberPanel instances in October 2024. A public PoC and a Nuclei scanning template exist, so unpatched internet-facing instances get found and compromised automatically, not by targeted actors. CyberPanel itself is general server-management software rather than an AI framework, but it is commonly used to host self-managed application stacks — including self-hosted AI/ML workloads such as inference servers, model dashboards, or RAG backends — so a compromised panel hands an attacker root-level control over anything colocated on that box, including model weights, API keys, and database credentials. Patch immediately to the fixed commit (5b08cd6 or later — verify your CyberPanel release actually ships the fix, since 2.3.7 was still unpatched at disclosure), and until patched, block or restrict access to /dataBases/upgrademysqlstatus and watch for anomalous outbound traffic or mass file encryption consistent with PSAUX IOCs.
Is CVE-2024-51567 actively exploited?
Yes, CVE-2024-51567 is confirmed actively exploited and listed in CISA Known Exploited Vulnerabilities catalog since Thu Nov 07 2024 00:00:00 GMT+0000 (Coordinated Universal Time).
How to fix CVE-2024-51567?
1) Patch to the fixed commit 5b08cd6 or later immediately; confirm your installed version actually includes the fix (2.3.7 was still unpatched at time of disclosure per the advisory). 2) If immediate patching isn't possible, block or firewall access to /dataBases/upgrademysqlstatus and any non-POST access to secMiddleware-protected routes. 3) Deploy a WAF/reverse-proxy rule to strip or reject shell metacharacters in the statusfile parameter. 4) Scan your own perimeter with the public Nuclei template to confirm exposure before an attacker does. 5) Hunt for PSAUX ransomware IOCs (unexpected encrypted files, ransom notes, unusual cron/systemd persistence) on any CyberPanel host. 6) Network-segment CyberPanel-managed hosts away from AI/ML secrets stores (model registries, vector DBs, inference API keys) so a panel compromise doesn't cascade. 7) Since CISA KEV due date (2024-11-28) has passed, treat any still-unpatched instance as a compliance gap for federal/regulated environments.
What systems are affected by CVE-2024-51567?
This vulnerability affects the following AI/ML architecture patterns: Self-hosted AI/ML hosting infrastructure, Model serving endpoints, Web-based admin/management UIs for AI workloads.
What is the CVSS score for CVE-2024-51567?
CVE-2024-51567 has a CVSS v3.1 base score of 10.0 (CRITICAL). The EPSS exploitation probability is 86.63%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0006 Active Scanning AML.T0049 Exploit Public-Facing Application AML.T0050 Command and Scripting Interpreter Compliance Controls Affected
What are the technical details?
Original Advisory
upgrademysqlstatus in databases/views.py in CyberPanel (aka Cyber Panel) before 5b08cd6 allows remote attackers to bypass authentication and execute arbitrary commands via /dataBases/upgrademysqlstatus by bypassing secMiddleware (which is only for a POST request) and using shell metacharacters in the statusfile property, as exploited in the wild in October 2024 by PSAUX. Versions through 2.3.6 and (unpatched) 2.3.7 are affected.
Exploitation Scenario
An attacker mass-scans the internet for exposed CyberPanel instances (typically port 8090), then sends an unauthenticated GET request to /dataBases/upgrademysqlstatus — exploiting the fact that secMiddleware only enforces checks on POST requests. By embedding shell metacharacters in the statusfile parameter, the attacker achieves arbitrary command execution as root on the underlying server. If that server also hosts a self-managed AI/ML stack (e.g., an internal LLM inference API, a RAG pipeline, or a model-serving dashboard), the attacker pivots to exfiltrate model weights, API keys, and vector-store contents, or simply deploys ransomware (as seen with PSAUX) to encrypt the entire host, taking down both the panel and any AI services running alongside it.
CVSS Vector
CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:N References
- cwe.mitre.org/data/definitions/420.html
- cwe.mitre.org/data/definitions/78.html
- cyberpanel.net/KnowledgeBase/home/change-logs/
- cyberpanel.net/blog/detials-and-fix-of-recent-security-issue-and-patch-of-cyberpanel
- dreyand.rs/code/review/2024/10/27/what-are-my-options-cyberpanel-v236-pre-auth-rce
- github.com/usmannasir/cyberpanel/commit/5b08cd6d53f4dbc2107ad9f555122ce8b0996515
- bleepingcomputer.com/news/security/massive-psaux-ransomware-attack-targets-22-000-cyberpanel-instances/
Timeline
Scanner Template Available
A Nuclei vulnerability scanner template exists for this CVE. You can scan your infrastructure for this vulnerability immediately.
View template on GitHubnuclei -t http/cves/2024/CVE-2024-51567.yaml -u https://target.example.com Related Vulnerabilities
CVE-2025-5120 10.0 smolagents: sandbox escape enables unauthenticated RCE
Same attack type: Code Execution CVE-2025-59528 10.0 Flowise: Unauthenticated RCE via MCP config injection
Same attack type: Code Execution CVE-2025-2828 10.0 LangChain RequestsToolkit: SSRF exposes cloud metadata
Same attack type: Auth Bypass CVE-2025-53767 10.0 Azure OpenAI: SSRF EoP, no auth required (CVSS 10)
Same attack type: Auth Bypass CVE-2024-2912 10.0 BentoML: RCE via insecure deserialization (CVSS 10)
Same attack type: Code Execution