CVE-2024-52407
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 BasePress BasePress Migration Tools basepress-migration-tools allows Upload a Web Shell to a Web Server.This issue affects BasePress Migration Tools: from n/a through <= 1.0.0.
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 confidenceThe BasePress Migration Tools plugin <= 1.0.0 contains an unrestricted file upload vulnerability that allows authenticated attackers to upload arbitrary executable files (including PHP web shells) to the web server, achieving remote code execution and complete site 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.
-
Verify BasePress Migration Tools plugin is installedNavigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'basepress-migration-tools' or similarAffected if The plugin is present on the WordPress site
-
Identify the installed plugin versionCheck the plugin header in main plugin file (usually basepress-migration-tools.php) for 'Version:' comment, or view in WordPress Plugins pageAffected if Unable to confirm version is newer than any patched release (no specific safe version documented)
-
Confirm authentication requirementsReview plugin settings and user role requirements for migration tool access; check if any WordPress user role has access to migration/import featuresAffected if Users with subscriber-level or higher authentication can access the migration upload functionality
-
Inspect upload directory for suspicious filesCheck /wp-content/uploads/ and any custom migration upload directories for unfamiliar .php, .phtml, .js, or other web-accessible executable filesAffected if Unexpected script files exist in upload directories, especially with randomized or suspicious names
-
Review web server access logs for upload activitySearch HTTP access logs for POST requests to migration tool endpoints containing .php file uploadsAffected if Evidence of PHP or other executable file types being uploaded via the plugin
If BasePress Migration Tools plugin is installed and the migration/upload feature is accessible to authenticated users, the site is potentially vulnerable to remote code execution via unrestricted file upload.
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 dataImmediately disable or remove the affected plugin until a secure version with proper file type validation and upload restrictions is available. Implement web server-level restrictions to block executable file uploads as an interim measure.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52407 — 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-52407 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