dbcve.org
1panelApplication · Fit2cloud

CVE-2025-54424

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-01
Fix available
A fix is available. Upgrade to 2.0.6 or later.
See remediation →
100/100
Remediation priority · Urgent
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
1Panel is a web interface and MCP Server that manages websites, files, containers, databases, and LLMs on a Linux server. In versions 2.0.5 and below, the HTTPS protocol used for communication between the Core and Agent endpoints has incomplete certificate verification during certificate validation, leading to unauthorized interface access. Due to the presence of numerous command execution or high-privilege interfaces in 1Panel, this results in Remote Code Execution (RCE). This is fixed in version 2.0.6. The CVE has been translated from Simplified Chinese using GitHub Copilot.

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

1Panel versions 2.0.5 and below have incomplete TLS certificate verification when Core and Agent endpoints communicate over HTTPS. This allows a man-in-the-middle attacker to intercept traffic and gain unauthorized access to high-privilege interfaces that expose command execution functionality, leading to Remote Code Execution.

MitigationUpgrade 1Panel to version 2.0.6 or later. If immediate upgrade is not possible, restrict network access to the Core-Agent communication channel to trusted IPs only.

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
1panelApplication
Affected:< 2.0.6

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 if 1Panel is installed
    Check for 1Panel installation by looking for its default installation directory or running '1pctl --version' if the 1Panel CLI is available
    Affected if 1Panel is installed on the system
  2. Determine the installed 1Panel version
    Run '1pctl --version' or check the version file typically located in the 1Panel installation directory
    Affected if The installed version is below 2.0.6 (versions 2.0.5 and below are affected)
  3. Verify Core-Agent communication is configured
    Check if the Core-Agent component is enabled by reviewing 1Panel configuration files or running '1pctl list' to see active components
    Affected if Core-Agent communication is configured and active in the environment
  4. Confirm HTTPS is used for Core-Agent traffic
    Review 1Panel configuration to verify that HTTPS/TLS is configured for Core-Agent communication, typically found in the application.yml or similar config file
    Affected if HTTPS is configured for Core-Agent communication (the vulnerability affects HTTPS connections with incomplete certificate verification)

A user is affected if they have 1Panel installed with a version below 2.0.6 AND have Core-Agent communication configured over HTTPS.

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.0.6 or later
Fixed in 2.0.6
Vendor patch github.com →
Interim mitigation

Upgrade 1Panel to version 2.0.6 or later. If immediate upgrade is not possible, restrict network access to the Core-Agent communication channel to trusted IPs only.

Recommended fix High confidence

2.0.6

  1. 1. Back up your current 1Panel installation and configuration
  2. 2. Upgrade 1Panel to version 2.0.6 or later
  3. 3. Verify the upgrade was successful by checking the version number in the web interface
  4. 4. Ensure HTTPS certificate verification is properly configured between Core and Agent endpoints

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

Fix this in 1panel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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