Cyber Resilience

CVE-2024-32047

Cyberpower Powerpanel ≤ 4.9.0

Published
15 May 2024
Modified
30 July 2025
Patch / advisory
View advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0051 41th percentile
Risk Priority 70 floored blend · peak EPSS

Summary

CVE-2024-32047 is a critical-severity Active Debug Code (CWE-489) vulnerability in Cyberpower Powerpanel. Its CVSS base score is 9.8 (Critical).

Operationally, ranked at the 41th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A02:2025 Security Misconfiguration

EU & UK References

Vulnerability Data

Hard-coded credentials for the CyberPower PowerPanel test server can be found in the production code. This might result in an attacker gaining access to the testing or production server.

CWE(s)
CWE-489

Related Threats

CVEs Like This One

CVE-2023-25131Same product: Cyberpower Powerpanel
CVE-2024-31409Same product: Cyberpower Powerpanel
CVE-2024-32737Same product: Cyberpower Powerpanel
CVE-2024-32735Same product: Cyberpower Powerpanel
CVE-2024-31856Same product: Cyberpower Powerpanel
CVE-2024-32739Same product: Cyberpower Powerpanel
CVE-2023-25132Same product: Cyberpower Powerpanel
CVE-2024-32738Same product: Cyberpower Powerpanel
CVE-2023-25133Same product: Cyberpower Powerpanel
CVE-2024-32736Same product: Cyberpower Powerpanel

Affected Assets

cyberpower
powerpanel
≤ 4.9.0

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

SC-25 Thin Nodes
addresses: CWE-489

Minimal functionality precludes inclusion of active debug code or diagnostic interfaces.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require removal of debug code before release, covering most of this weakness while the control addresses many other development issues.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development and acceptance catches active debug code before deployment.

A.8.9 Configuration management mostly match
prevents

Configuration management can disable or remove debug features through hardened baselines.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates removal of debug code before release.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly prohibit leaving debug code active in production.

A.8.31 Separation of development, test and production environments partial match
prevents

Separation of environments reduces risk of debug code reaching production but does not directly address its removal.

A.8.32 Change management partial match
prevents

Change management can enforce removal of debug code as part of release gates.

References