CVE-2024-2024

HIGH

Folders Pro <= 3.0.2 - Authenticated(Author+) Arbitrary File Upload via handle_folders_file_upload

Title source: CVE List
Search associated code STIX 2.1 vulnerability STIX 2.1 with PoCs

Record summary

CVE-2024-2024 has a selected CVSS score of 8.8 (high); EIP currently links 18 repository PoCs and 1 lab environment.

Description

The Folders Pro plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'handle_folders_file_upload' function in all versions up to, and including, 3.0.2. This makes it possible for authenticated attackers, with author access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

Description source: CVE List

Exploitation context

Available material

Repository PoCs
18
Lab environments
1

CISA SSVC decision

ExploitationNone
AutomatableNo
Technical impactTotal

CISA Coordinator · SSVC 2.0.3 · Evaluated Jun 15, 2024 · Source: CVE List

Affected products and versions

1
ProductSourceVersion range

Folders Pro

Browse Premio / Folders Pro

Default status: unaffected

CVE ListThrough 3.0.2affected

Proofs of concept

Showing 12 of 18

Repository PoCs

GitHubbuluma/ansible-role-cve_2024_3094Repository PoCby buluma0Not analyzed43 files

47.5 KiB · linked to 2 vulnerabilities

GitHub
PoC details
GitHubStuub/RCity-CVE-2024-27198Repository PoCby Stuub36Not analyzed2 files

26.2 KiB · linked to 3 vulnerabilities

GitHub
PoC details
GitHubambionics/cnext-exploitsRepository PoCby ambionics505Not analyzed21 files

182.9 KiB · linked to 2 vulnerabilities

GitHub
PoC details
GitHubChocapikk/CVE-2024-5084Repository PoCby Chocapikk9Not analyzed3 files

6.8 KiB · linked to 2 vulnerabilities

GitHub
PoC details
GitHub0nin0hanz0/CVE-2024-24919-PoCRepository PoCby 0nin0hanz012Not analyzed4 files

981.9 KiB · linked to 2 vulnerabilities

GitHub
PoC details
GitHubdream434/CVE-2024-29269Repository PoCby Jhonsonwannaa0Not analyzed3 files

2.5 KiB · linked to 2 vulnerabilities

GitHub
PoC details
GitHubdream434/CVE-2024-31819Repository PoCby Jhonsonwannaa0Not analyzed4 files

10.4 KiB · linked to 2 vulnerabilities

GitHub
PoC details
GitHubwiggels/regresshion-checkRepository PoCby wiggels6Not analyzed6 files

25.8 KiB · linked to 2 vulnerabilities

GitHub
PoC details
GitHubrobertdfrench/ifuncd-upRepository PoCby robertdfrench60Not analyzed39 files

2.1 MiB · linked to 2 vulnerabilities

GitHub
PoC details
GitHubtoneemarqus/CVE-2024-39031Repository PoCby toneemarqus0Not analyzed1 file

2.8 KiB · linked to 2 vulnerabilities

GitHub
PoC details
GitHubl0n3m4n/CVE-2024-22274-RCERepository PoCby l0n3m4n45Not analyzed10 files

1.3 MiB · linked to 2 vulnerabilities

GitHub
PoC details
GitHubexploits-forsale/collateral-damageRepository PoCby exploits-forsale529Not analyzed26 files

1.1 MiB · linked to 2 vulnerabilities

GitHub
PoC details

Search the exploit catalog for CVE-2024-2024

Docker lab environments

1
GitHub

Repository root

robertdfrench/ifuncd-upCreated Vuln labCVE-2024-2024CVE-2024-3094Dockerfile

1 Dockerfile

View exploit
Analysisdeepseek-v4-pro:cloud ·

Environment assessment

A Debian Bookworm container with build tools, GDB, and vim, intended as a development/analysis workspace for exploring GNU IFUNC and its role in CVE-2024-3094.

Dockerfile:1-20README.md:1-622

Lab assessment

Vulnerability lab

The README explicitly discusses CVE-2024-3094, analyzes GNU IFUNC as a vulnerability, and provides code examples demonstrating IFUNC behavior. The Dockerfile sets up a workspace with build tools and GDB, consistent with a vulnerability research environment.

README.md:1-622Dockerfile:1-20
Lab shapeDockerfile
ServicesUnknown
Compose manifests0
Dockerfiles1
Evidence & reasoningComponents · CVE assessment · exercise context · review boundaries
Components

Services and files described by the evidence

debian:bookworm base image

base operating system

Provides the Debian Bookworm environment for the container.

Dockerfile:1

build-essential

compilation toolchain

Installed to compile C code examples in the repository.

Dockerfile:4

gdb

debugger

Installed for debugging compiled programs, likely to analyze IFUNC behavior.

Dockerfile:5

bsdextrautils

utility

Provides the 'column' command, possibly for formatting output in demos.

Dockerfile:6

time

performance measurement

Installed to measure execution time of speed demos.

Dockerfile:7

man-db

documentation

Installed for manual pages.

Dockerfile:8

checksec

security analysis

Installed to check binary security features, relevant to vulnerability analysis.

Dockerfile:9

vim

text editor

Installed and configured for editing source code within the container.

Dockerfile:12-13

/workspace

working directory

Set as the working directory for the container.

Dockerfile:16

bash shell

interactive entrypoint

Keeps the container running with an interactive bash shell.

Dockerfile:19
CVE assessment

How the supplied evidence relates each vulnerability

CVE-2024-2024

Insufficient evidence

CVE-2024-2024 is not mentioned in any supplied evidence file. The README and other files only discuss CVE-2024-3094.

CVE-2024-3094

Supported by supplied evidence

The README extensively discusses CVE-2024-3094, its relation to GNU IFUNC, and provides code examples demonstrating the IFUNC mechanism used in the backdoor.

README.md:1-622
Exercise context

Requirements and sequence described by the evidence

Prerequisites

  • Docker must be installed to build and run the container.Dockerfile:1-20
  • The repository source code must be mounted or copied into the container to compile and run the examples.Dockerfile:16

Evidence-described exercise path

  1. Build the Docker image from the provided Dockerfile.Dockerfile:1-20
  2. Run the container with the repository source mounted at /workspace.Dockerfile:16
  3. Compile and run the IFUNC demonstration programs (e.g., cpu_demo.c, tty_demo.c) to observe IFUNC behavior.code/cpu_demo.c:1-69code/tty_demo.c:1-52
  4. Use GDB to debug the compiled binaries and inspect the Global Offset Table and resolver execution.Dockerfile:5
  5. Run the speed demos to compare performance of IFUNC versus function pointers.README.md:1-622
Safety-review evidence

Behaviors behind the stored safety assessment

No harmful behavior observed

The Dockerfile installs standard development tools and sets an interactive bash shell. No network services are exposed, no privileged mode is requested, and no evidence of host escape, persistence, or external communication is present. The README and code examples are educational and focused on the IFUNC vulnerability.

Dockerfile:1-20README.md:1-622
Review boundaries

What the analysis did not establish

  • CVE-2024-2024 is not referenced in any supplied evidence; its association is unsupported.
  • The packet does not include a docker-compose file or runtime configuration, so port mappings or volume mounts are unknown.
  • Binary files (images, memes) are present but not inspected; they are not expected to contain executable code.
Model interpretation

This review is limited to the supplied lab evidence packet. It does not assert that the environment runs, reproduces a vulnerability, or is safe to execute. Contract: eip-docker-lab-analysis-v1.

References

3