CVE-2024-48034
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnrestricted 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe fliperrr Creates 3D Flipbook, PDF Flipbook WordPress plugin (versions <= 1.2) contains an unrestricted file upload vulnerability that allows authenticated attackers to upload dangerous file types (such as web shells) directly to the web server, potentially achieving remote code execution and full server compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if the fliperrr plugin is installedIn the WordPress admin dashboard, navigate to Plugins > Installed Plugins and look for 'fliperrr Creates 3D Flipbook, PDF Flipbook' or check the /wp-content/plugins/ directory for a folder containing 'fliperrr' in the nameAffected if The plugin is present on the WordPress site
-
Determine the installed plugin versionIn WordPress admin, click on the plugin to view its details and locate the version number, or inspect the plugin's main PHP file for a 'Version' header commentAffected if The installed version is 1.2 or any version lower than 1.2
-
Verify if file upload functionality is accessibleLocate the upload endpoint or feature used by the plugin (typically found in plugin settings or frontend flipbook creation forms) and confirm it accepts file uploadsAffected if The file upload feature exists and is accessible to authenticated users (any logged-in user)
-
Check authentication requirements for uploadsTest the upload functionality with a low-privilege WordPress user account (subscriber level) to confirm whether authentication alone is sufficient to access the upload featureAffected if Any authenticated user (regardless of role/privilege) can access and use the file upload feature
The environment is affected if the fliperrr plugin version 1.2 or lower is installed and its file upload feature is accessible to authenticated users without restrictive validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict file uploads to only allow safe file types (PDF, images), implement server-side MIME type and extension validation, rename uploaded files, store uploads outside the web root, and update to a patched version when available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48034 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-48034 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data