dbcve.org
PowerpanelApplication · Cyberpower

CVE-2024-32738

HIGH · 7.5 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 2.8.3 or later.
See remediation →
84/100
Remediation priority · High
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
A sql injection vulnerability exists in CyberPower PowerPanel Enterprise prior to v2.8.3. An unauthenticated remote attacker can leak sensitive information via the "query_ptask_lean" function within MCUDBHelper.

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

A SQL injection vulnerability exists in CyberPower PowerPanel Enterprise's MCUDBHelper component, specifically in the 'query_ptask_lean' function. An unauthenticated remote attacker can exploit this to inject malicious SQL queries and leak sensitive information from the database.

MitigationUpgrade to CyberPower PowerPanel Enterprise v2.8.3 or later. If immediate patching is not possible, implement web application firewall (WAF) rules to detect and block SQL injection attempts targeting the affected endpoint.

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:< 2.8.3

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 PowerPanel Enterprise installation
    Locate the PowerPanel Enterprise installation directory or service on the system. Common paths include C:\Program Files\CyberPower PowerPanel Enterprise or /opt/cyberpower/powerpanel. Check for running processes named PowerPanel or related services.
    Affected if PowerPanel Enterprise is not found on the system, the vulnerability does not apply.
  2. Determine installed version
    Check the version of CyberPower PowerPanel Enterprise installed. This is typically available in the web interface (About page), installation logs, or version files within the installation directory. Compare this version against the affected range.
    Affected if The installed version is below 2.8.3 (e.g., 2.8.2, 2.8.1, 2.8.0, or earlier).
  3. Verify MCUDBHelper component exposure
    Determine if the MCUDBHelper web component is exposed and accessible. This is typically accessed via HTTP/HTTPS endpoints on the PowerPanel web interface. Check network configuration to confirm the management interface is network-accessible.
    Affected if The MCUDBHelper component is exposed to network traffic without proper access controls.
  4. Confirm vulnerable endpoint accessibility
    If possible, verify the query_ptask_lean function endpoint is reachable. This involves checking if the web API endpoints related to MCUDBHelper are accessible to unauthenticated users.
    Affected if The vulnerable endpoint is accessible without authentication.

A system is affected if CyberPower PowerPanel Enterprise is installed with a version lower than 2.8.3 and the MCUDBHelper component is network-accessible.

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.8.3 or later
Fixed in 2.8.3
Interim mitigation

Upgrade to CyberPower PowerPanel Enterprise v2.8.3 or later. If immediate patching is not possible, implement web application firewall (WAF) rules to detect and block SQL injection attempts targeting the affected endpoint.

Recommended fix High confidence

PowerPanel Enterprise v2.8.3

  1. Verify current PowerPanel Enterprise version via the admin interface or system information
  2. Download PowerPanel Enterprise v2.8.3 or later from the official CyberPower website (www.cyberpower.com)
  3. Review release notes for v2.8.3 to confirm security fixes
  4. Create a full backup of the current PowerPanel configuration and database
  5. Follow CyberPower's official upgrade documentation to apply the v2.8.3 update
  6. After upgrade, verify the version number reflects v2.8.3 or later
  7. Test critical PowerPanel functions to ensure normal operation
Caveat Standard security patch upgrade - review release notes for any configuration changes

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

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-2024-32738 — 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-32738 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