# CVE-2024-48034: WordPress Creates 3D Flipbook, PDF Flipbook plugin <= 1.2 - Arbitrary File Upload vulnerability

> An attacker can upload a web shell to the server via the Creates 3D Flipbook, PDF Flipbook plugin, leading to remote code execution.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** 16 Oct 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-8p2h-8vgw-6jmp

## What is CVE-2024-48034?

CVE-2024-48034 is a critical vulnerability in fliperrr Creates 3D Flipbook, PDF Flipbook, published on 16 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unrestricted Upload of File with Dangerous Type vulnerability in fliperrr Creates 3D Flipbook, PDF Flipbook create-flipbook-from-pdf allows Upload a Web Shell to a Web Server.This issue affects Creates 3D Flipbook, PDF Flipbook: from n/a through <= 1.2.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2024-48034 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48034 is a critical vulnerability in fliperrr Creates 3D Flipbook, PDF Flipbook, published on 16 Oct 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-48034 exists.

Affected product: fliperrr Creates 3D Flipbook, PDF Flipbook. 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-48034/ (Markdown: https://insights.sbomify.com/CVE-2024-48034/index.md)
```

## Sources

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

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