# CVE-2024-33615: CyberPower PowerPanel business Relative Path Traversal

> Attackers can upload malicious Zip files to write arbitrary files and achieve remote code execution on CyberPower PowerPanel Business servers.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-694q-5223-w869

## What is CVE-2024-33615?

CVE-2024-33615 is a high-severity path traversal vulnerability in CyberPower PowerPanel business, published on 15 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A specially crafted Zip file containing path traversal characters can be
 imported to the 
CyberPower PowerPanel 

server, which allows file writing to the server outside
 the intended scope, and could allow an attacker to achieve remote code 
execution.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2024-33615?


## How do I fix CVE-2024-33615?

No fix has been published for CVE-2024-33615 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-33615 being exploited?

There is no known exploitation of CVE-2024-33615 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-33615 and fix it if it is affected.

What it is: CVE-2024-33615 is a high-severity path traversal vulnerability in CyberPower PowerPanel business, published on 15 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-33615 in the wild and no public exploit code.

Affected product: CyberPower PowerPanel business. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-33615/ (Markdown: https://insights.sbomify.com/CVE-2024-33615/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-33615
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-33615
- OSV: https://osv.dev/vulnerability/CVE-2024-33615

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-33615/
Summaries are generated and may contain mistakes; the official description above is the record.