dbcve.org
PowerpanelApplication · Cyberpower

CVE-2023-25133

CRITICAL · 9.8 CVSS v3.1 Published 2023-04-24
Fix available
A fix is available. Upgrade to after 4.8.6 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Improper privilege management vulnerability in default.cmd file in PowerPanel Business Local/Remote for Windows v4.8.6 and earlier, PowerPanel Business Management for Windows v4.8.6 and earlier, PowerPanel Business Local/Remote for Linux 32bit v4.8.6 and earlier, PowerPanel Business Local/Remote for Linux 64bit v4.8.6 and earlier, PowerPanel Business Management for Linux 32bit v4.8.6 and earlier, PowerPanel Business Management for Linux 64bit v4.8.6 and earlier, PowerPanel Business Local/Remote for MacOS v4.8.6 and earlier, and PowerPanel Business Management for MacOS v4.8.6 and earlier allows remote attackers to execute operation system commands via unspecified vectors.

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

An improper privilege management vulnerability exists in the default.cmd batch script file of PowerPanel Business software (versions 4.8.6 and earlier) across Windows, Linux, and MacOS platforms. The vulnerability allows remote attackers to execute operating system commands due to the script running with elevated or inappropriate privileges. The CVSS 9.8 score indicates trivial exploitability with complete system compromise potential.

MitigationUpgrade PowerPanel Business to a version newer than 4.8.6. If immediate patching is not possible, restrict access to the default.cmd file and disable or rename the script to prevent unauthorized execution, while reviewing service account privileges.

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
PowerpanelApplication
Affected:<= 4.8.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 PowerPanel Business is installed
    On Windows, check Program Files for 'PowerPanel Business' folder or use 'Get-ItemProperty' on registry key 'HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\PowerPanel Business'. On Linux/Mac, check common installation directories like /opt or /Applications.
    Affected if PowerPanel Business software is found on the system
  2. Determine the installed PowerPanel Business version
    On Windows, right-click the PowerPanel Business application in Control Panel > Programs and check the version field, or run the application and look in Help > About. On Linux/Mac, check the version information in the application or installation package.
    Affected if The installed version is 4.8.6 or earlier
  3. Locate the default.cmd batch script file
    Search for the file named 'default.cmd' within the PowerPanel installation directory. Common locations include the main installation folder or subdirectories related to scripts or configuration.
    Affected if The file default.cmd exists in the PowerPanel installation directory
  4. Check the file permissions on default.cmd
    On Windows, right-click default.cmd > Properties > Security to view which users and groups have read, write, or execute permissions. On Linux/Mac, use 'ls -l' command on the file to inspect permission bits and ownership.
    Affected if The file has overly permissive access controls allowing unauthorized users to modify or execute it, or runs with elevated privileges

A system is affected if PowerPanel Business version 4.8.6 or earlier is installed and the default.cmd script file exists with elevated or excessive privileges.

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.

From vendor data
Upgrade available Upgrade to a release after 4.8.6
Interim mitigation

Upgrade PowerPanel Business to a version newer than 4.8.6. If immediate patching is not possible, restrict access to the default.cmd file and disable or rename the script to prevent unauthorized execution, while reviewing service account privileges.

Fix this in Powerpanel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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