dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 28 Nov 2024. Known ransomware use
CyberpanelApplication

CVE-2024-51567

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-29
Fix available
A fix is available. Upgrade to 2.3.8 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

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
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.

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

CyberPanel versions through 2.3.7 contain an authentication bypass and command injection vulnerability in the upgrademysqlstatus endpoint. The secMiddleware, which enforces authentication, only applies to POST requests, allowing attackers to bypass it using GET requests to /dataBases/upgrademysqlstatus. Additionally, the statusfile parameter accepts shell metacharacters enabling arbitrary command execution. This was actively exploited in the wild in October 2024.

MitigationImmediately upgrade CyberPanel to the latest version or apply the fix at commit 5b08cd6. If immediate patching is not possible, restrict access to the /dataBases/ endpoint via firewall or web server configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CyberpanelApplication
Affected:< 2.3.8

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Identify CyberPanel version
    Check the installed CyberPanel version by running: grep -r 'VERSION' /usr/local/CyberPanel/__init__.py or cat /usr/local/CyberPanel/version
    Affected if The installed version is lower than 2.3.8 (e.g., 2.3.7, 2.3.6, etc.)
  2. Locate the vulnerable endpoint
    Verify the upgrademysqlstatus.py file exists in the dataBases directory: find /usr/local/CyberPanel -path '*/dataBases/upgrademysqlstatus.py' -type f
    Affected if The file exists and the CyberPanel version is below 2.3.8
  3. Check secMiddleware configuration
    Examine the secMiddleware implementation in CyberPanel to confirm it only enforces authentication on POST requests, not GET requests to /dataBases/upgrademysqlstatus
    Affected if secMiddleware only validates POST requests, allowing unauthenticated GET access to the endpoint
  4. Verify network exposure
    Confirm the CyberPanel web interface (usually port 8090) is exposed to the network or internet and the /dataBases/upgrademysqlstatus endpoint is reachable via HTTP/HTTPS
    Affected if The endpoint is accessible from untrusted networks without authentication

You are affected if CyberPanel version is below 2.3.8 AND the /dataBases/upgrademysqlstatus endpoint is network-accessible, allowing unauthenticated GET requests that can inject shell commands via the statusfile parameter.

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
Upgrade available Upgrade to 2.3.8 or later
Fixed in 2.3.8
Vendor patch dreyand.rs →
Interim mitigation

Immediately upgrade CyberPanel to the latest version or apply the fix at commit 5b08cd6. If immediate patching is not possible, restrict access to the /dataBases/ endpoint via firewall or web server configuration.

Recommended fix High confidence

CyberPanel 2.3.8

  1. 1. Create a complete backup of your CyberPanel installation, including all websites, databases, and configuration files.
  2. 2. Log into the CyberPanel admin interface or access your server via SSH.
  3. 3. If using SSH, run the CyberPanel upgrade script: 'sh <(curl https://cyberpanel.net/install.sh || wget -O - https://cyberpanel.net/install.sh)' and select the upgrade option, or use 'cyberpanel-upgrade' if available.
  4. 4. Alternatively, run the update command via CLI: 'apt-get update && apt-get install cyberpanel' (for Ubuntu/Debian) or 'yum update cyberpanel' (for CentOS/RHEL).
  5. 5. After installation completes, restart the CyberPanel services: 'systemctl restart lscpd' and 'systemctl restart gunicorn'.
  6. 6. Verify the upgrade was successful by checking the CyberPanel version in the admin dashboard (bottom-left corner) or running: 'cat /usr/local/CyberPanel/version.txt' or 'ls -la /usr/local/CyberPanel/'.
  7. 7. Confirm the version shows 2.3.8 or later which contains the fix for CVE-2024-51567.

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

Fix this in Cyberpanel Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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