Wp Quick SetupWordPress extension · Antonhoelstad
CVE-2024-52429
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 AntonHoelstad WP Quick Setup wp-quick-setup allows Upload a Web Shell to a Web Server.This issue affects WP Quick Setup: from n/a through <= 2.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 WP Quick Setup WordPress plugin versions through 2.0 contains an unrestricted file upload vulnerability that allows authenticated attackers to upload dangerous file types (including PHP web shells) to the web server without proper validation or sanitization, potentially achieving remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp Quick SetupWordPress extension
<= 2.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 WP Quick Setup plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for the 'wp-quick-setup' folder, or navigate to WP Admin > Plugins and look for 'WP Quick Setup' by Antonhoelstad in the installed plugins list.Affected if The plugin is present in the WordPress installation.
-
Determine installed plugin versionIn WordPress Admin, go to Plugins > Installed Plugins > WP Quick Setup and read the version number displayed below the plugin name. Alternatively, open wp-content/plugins/wp-quick-setup/readme.txt and check the 'Stable tag' or version line in the file header.Affected if The installed version is 2.0 or any version lower than 2.0.
-
Confirm plugin is activeIn WordPress Admin, go to Plugins > Installed Plugins and check if WP Quick Setup shows as 'Active' rather than 'Inactive' or 'Must-Use'.Affected if The plugin is currently activated.
-
Inspect upload directories for suspicious filesExamine the wp-content/uploads/ directory (and any custom upload paths configured in WordPress Media settings) for any .php files, .phtml files, or other executable file types that should not be present in upload folders. Use a command like: find wp-content/uploads/ -name '*.php' -o -name '*.phtml' -o -name '*.phar'.Affected if Any PHP files or other executable scripts are found in upload directories, especially if they were not intentionally uploaded through trusted means.
-
Check for recently modified PHP files in the plugin folderReview the wp-content/plugins/wp-quick-setup/ directory for any unexpected new files or recently modified PHP files that may indicate compromise. Use: find wp-content/plugins/wp-quick-setup/ -type f -name '*.php' -mtime -7 (adjust timeframe as needed).Affected if Unexpected new or modified PHP files exist in the plugin directory.
-
Audit WordPress users with upload capabilitiesIn WordPress Admin, go to Users and review accounts with roles that grant upload permissions (Administrator, Editor, Author, or any custom role with upload_file capability). Identify any unrecognized or suspicious user accounts.Affected if There are user accounts with upload permissions that were not created by known administrators.
Your environment is affected if the WP Quick Setup plugin version 2.0 or below is installed and active, or if suspicious executable files are found in upload directories.
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 WP Quick Setup plugin, audit the server for any recently uploaded suspicious files (especially .php files in upload directories), and implement proper file type validation with whitelist checking before allowing any file uploads.
Fix this in Wp Quick Setup
Scoped from the published advisory
- 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-52429 — 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-52429 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