# CVE-2024-2023: Folders <= 3.0 and Folders Pro <= 3.0.2 - Directory Traversal via handle_folders_file_upload

> Authenticated attackers with author access can upload files to arbitrary server locations via directory traversal in the Folders plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 14 Jun 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-qqvh-qhvc-6p93

## What is CVE-2024-2023?

CVE-2024-2023 is a medium-severity path traversal vulnerability in Premio Folders Pro, published on 14 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Folders and Folders Pro plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 3.0 in Folders and 3.0.2 in Folders Pro via the 'handle_folders_file_upload' function. This makes it possible for authenticated attackers, with author access and above, to upload files to arbitrary locations on the server.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2024-2023 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2023 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2023 is a medium-severity path traversal vulnerability in Premio Folders Pro, published on 14 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2023 exists.

Affected product: Premio Folders Pro. 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-2023/ (Markdown: https://insights.sbomify.com/CVE-2024-2023/index.md)
```

## Sources

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

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