CVE-2024-49652
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 Renata Bracichowicz 3D Work In Progress renee-work-in-progress allows Upload a Web Shell to a Web Server.This issue affects 3D Work In Progress: from n/a through <= 1.0.3.
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 · high confidenceUnrestricted file upload vulnerability in the 3D Work In Progress WordPress plugin allows authenticated attackers to upload malicious PHP files (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.
-
Confirm 3D Work In Progress plugin is installedNavigate to WordPress admin > Plugins or inspect wp-content/plugins directory for '3d-work-in-progress' or similar namingAffected if Plugin directory exists in the WordPress installation
-
Identify installed plugin versionOpen the main plugin PHP file and locate the 'Version' header in the plugin comment block, or check the plugin admin panel detailsAffected if Version is unknown or matches any affected version range (compare against published CVE details)
-
Verify file upload functionality existsAccess the plugin settings or upload interface (typically at /wp-admin/admin-ajax.php or a dedicated plugin page) and inspect available upload endpointsAffected if Plugin provides a file upload feature accessible to authenticated users
-
Test for unrestricted PHP uploadUsing an authenticated session, attempt to upload a file with .php extension through the plugin upload form. Check if the file is accepted and accessible via web browserAffected if PHP files can be uploaded and accessed via web URL, indicating no server-side validation
-
Check upload storage locationInspect plugin configuration or examine the upload directory path where files are stored (typically in wp-content/uploads/)Affected if Uploaded files are stored within the web-accessible document root
User is affected if the 3D Work In Progress plugin is installed, provides an accessible upload feature, and allows PHP files to be uploaded to a web-accessible directory without proper 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 dataImplement strict server-side allowlist-based file type validation, store uploaded files outside the web root, disable script execution in upload directories, and apply vendor patch or replace the plugin if no patch is available.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49652 — 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-49652 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