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 25 Dec 2024. Known ransomware use
CyberpanelApplication

CVE-2024-51378

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
getresetstatus in dns/views.py and ftp/views.py in CyberPanel (aka Cyber Panel) before 1c0c6cb allows remote attackers to bypass authentication and execute arbitrary commands via /dns/getresetstatus or /ftp/getresetstatus 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 before 1c0c6cb contains an authentication bypass in the getresetstatus function in both dns/views.py and ftp/views.py. The secMiddleware only enforces authentication on POST requests, allowing attackers to bypass authentication entirely via GET requests to /dns/getresetstatus or /ftp/getresetstatus. Additionally, the statusfile parameter accepts shell metacharacters enabling arbitrary command execution. This was actively exploited in the wild in October 2024 by the PSAUX ransomware group.

MitigationApply the vendor patch (commit 1c0c6cb or later) or upgrade to a patched version of CyberPanel (2.3.7 patched). If immediate patching is not possible, block access to these endpoints at the WAF or reverse proxy level.

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. Locate CyberPanel installation directory
    Check common installation paths such as /usr/local/CyberPanel, /opt/lscp, or /home/cyberpanel. Look for directories containing CyberPanel-specific files like 'dns/views.py' or 'ftp/views.py'.
    Affected if CyberPanel is installed and the installation directory contains the vulnerable views.py files.
  2. Identify installed CyberPanel version
    Look for a version file in the installation directory, typically named 'version.txt' or check the git commit hash. Run: cat /usr/local/CyberPanel/version.txt 2>/dev/null or examine the git repository with: git -C /usr/local/CyberPanel rev-parse HEAD
    Affected if The version is lower than 2.3.8 or the git commit is before 1c0c6cb.
  3. Verify vulnerable endpoints are exposed
    Confirm the web server is running and accessible. Test if http(s)://<your-server>/dns/getresetstatus or /ftp/getresetstatus endpoints respond. Check your web server configuration for URL routing to these endpoints.
    Affected if These endpoints are accessible without authentication on the network.
  4. Inspect dns/views.py for vulnerable code pattern
    Open /usr/local/CyberPanel/dns/views.py and search for 'getresetstatus' function. Look for shell command execution using the 'statusfile' parameter, such as subprocess calls, os.system, or shell command construction without proper sanitization.
    Affected if The code contains command execution using the statusfile parameter without input validation.
  5. Inspect ftp/views.py for vulnerable code pattern
    Open /usr/local/CyberPanel/ftp/views.py and search for 'getresetstatus' function. Verify if it contains unsafe shell command construction with the statusfile parameter, similar to the dns/views.py vulnerability.
    Affected if The code contains command execution using the statusfile parameter without input validation.
  6. Check web server access logs for exploitation attempts
    Review access logs in /usr/local/lscp/logs/ or /var/log/lscp/ for requests to /dns/getresetstatus or /ftp/getresetstatus with shell metacharacters (|, ;, &, $ , `, etc.) in the statusfile parameter.

You are affected if CyberPanel version is below 2.3.8 (or git commit before 1c0c6cb) AND the vulnerable endpoints are exposed on your network without authentication.

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 github.com →
Interim mitigation

Apply the vendor patch (commit 1c0c6cb or later) or upgrade to a patched version of CyberPanel (2.3.7 patched). If immediate patching is not possible, block access to these endpoints at the WAF or reverse proxy level.

Recommended fix High confidence

CyberPanel 2.3.8

  1. 1. Back up your current CyberPanel installation and all critical data before upgrading.
  2. 2. Upgrade CyberPanel to version 2.3.8 or later. This can typically be done via the control panel's update function or by running the official upgrade script.
  3. 3. After upgrading, verify the version number has changed to 2.3.8 or higher in the CyberPanel admin interface.
  4. 4. Confirm the security patch is applied by checking that the vulnerable endpoints (/dns/getresetstatus and /ftp/getresetstatus) are no longer accessible without proper authentication and input validation.
Caveat Standard upgrade risks apply - test in staging first, and ensure backups are verified before production upgrade

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

Fix this in Cyberpanel Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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