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 Nov 2025.
WebpanelApplication · Control Webpanel

CVE-2025-48703

CRITICAL · 9.0 CVSS v3.1 Published 2025-09-19
Fix available
A fix is available. Upgrade to 0.9.8.1205 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

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
CWP (aka Control Web Panel or CentOS Web Panel) before 0.9.8.1205 allows unauthenticated remote code execution via shell metacharacters in the t_total parameter in a filemanager changePerm request. A valid non-root username must be known.

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

CWP (Control Web Panel) before version 0.9.8.1205 contains an unauthenticated remote code execution vulnerability in the filemanager module. The t_total parameter in the changePerm request accepts shell metacharacters without proper sanitization, allowing arbitrary command execution by attackers who also possess a valid non-root username.

MitigationUpdate CWP to version 0.9.8.1205 or later, which contains the security fix. If immediate patching is not possible, consider restricting access to the filemanager module or implementing WAF rules to block shell metacharacters in request parameters.

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
WebpanelApplication
Affected:< 0.9.8.1205

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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 installed CWP version
    Check the CWP version number on your system. This is typically visible in the CWP admin panel (Dashboard > System Information) or can be found in version-related files in the CWP installation directory.
    Affected if The installed version is lower than 0.9.8.1205
  2. Confirm filemanager module is active
    Verify that the filemanager component is enabled and accessible in your CWP installation. This is typically found under the CWP user panel or admin panel under file management features.
    Affected if The filemanager module is enabled and accessible to non-root users
  3. Check for the changePerm endpoint exposure
    Inspect if the filemanager's changePerm functionality is exposed via the web interface. This function handles permission changes and accepts the t_total parameter.
    Affected if The changePerm function in filemanager is reachable without additional access restrictions beyond normal authentication
  4. Verify non-root user accounts exist
    Confirm that there are non-root user accounts configured in CWP. These accounts would have access to the filemanager functionality.
    Affected if Non-root user accounts exist in the CWP system who can access the filemanager

Your environment is affected if CWP version is below 0.9.8.1205 AND the filemanager module is accessible to non-root users.

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 0.9.8.1205 or later
Fixed in 0.9.8.1205
Interim mitigation

Update CWP to version 0.9.8.1205 or later, which contains the security fix. If immediate patching is not possible, consider restricting access to the filemanager module or implementing WAF rules to block shell metacharacters in request parameters.

Recommended fix High confidence

CWP (Control Web Panel) version 0.9.8.1205 or later

  1. 1. Backup the current CWP (Control Web Panel) configuration and all user data before proceeding
  2. 2. Download the fixed version of Control Web Panel (version 0.9.8.1205 or later) from the official source at control-webpanel.com
  3. 3. Execute the official CWP upgrade script or installer for version 0.9.8.1205
  4. 4. After upgrade completes, verify the new version is installed by checking the CWP admin panel
  5. 5. Confirm the filemanager changePerm functionality is working correctly and the vulnerability is patched
  6. 6. Review CWP logs to ensure no exploitation attempts occurred prior to patching
Caveat Standard version upgrade - review official release notes for any required configuration changes or migration steps

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

Fix this in Webpanel Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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