CVE-2024-9290
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 · uneditedThe Super Backup & Clone - Migrate for WordPress plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation and a missing capability check on the ibk_restore_migrate_check() function in all versions up to, and including, 2.3.3. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
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 Super Backup & Clone - Migrate for WordPress plugin versions up to 2.3.3 contains an unauthenticated arbitrary file upload vulnerability in the ibk_restore_migrate_check() function. The function lacks both capability checks (allowing unauthenticated access) and file type validation, enabling attackers to upload arbitrary files including malicious PHP scripts that can lead to remote code execution.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check if Super Backup & Clone plugin is installedLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Super Backup & Clone - Migrate' in the list.Affected if The plugin appears in the installed plugins list
-
Determine the installed plugin versionIn the plugins list, view the details of 'Super Backup & Clone - Migrate' to find the version number. Alternatively, check the plugin header in the main plugin PHP file via file manager or FTP.Affected if Version is 2.3.3 or lower
-
Locate the vulnerable function in plugin filesAccess the plugin directory via FTP or file manager and search the plugin files for the string 'ibk_restore_migrate_check'. This function should exist in the affected versions.Affected if The function ibk_restore_migrate_check is found in the plugin code without additional authorization checks nearby
-
Check for suspicious uploaded filesSearch the wp-content directory, particularly the uploads folder and the plugin directory itself, for unexpected PHP files or other unrecognized files that may have been uploaded.Affected if Unexpected PHP files or scripts are found in the uploads folder or plugin directory
If the plugin is installed at version 2.3.3 or lower and contains the unprotected ibk_restore_migrate_check function, the environment is affected by this vulnerability.
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 dataUpdate the plugin to the latest version immediately. If no patch is available, disable and remove the plugin. Consider reviewing the server for any previously uploaded malicious files.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9290 — 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-9290 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