CVE-2024-56064
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 azzaroco WP SuperBackup indeed-wp-superbackup allows Upload a Web Shell to a Web Server.This issue affects WP SuperBackup: from n/a through <= 2.3.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 confidenceThe WP SuperBackup WordPress plugin (indeed-wp-superbackup) versions up to 2.3.3 contains an unrestricted file upload vulnerability allowing authenticated attackers to upload arbitrary files, including malicious PHP web shells, directly to the web server. This enables complete 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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check if WP SuperBackup plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP SuperBackup' or 'indeed-wp-superbackup'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'indeed-wp-superbackup' or similar.Affected if The plugin is present in the WordPress installation
-
Determine the installed version of WP SuperBackupIn WordPress admin, go to Plugins > Installed Plugins, find WP SuperBackup, and note the version number displayed. Compare this version to the affected range (versions up to 2.3.3).Affected if The installed version is 2.3.3 or any earlier version
-
Inspect the plugin upload directory for unexpected filesCheck the plugin's upload or backup directories (typically /wp-content/plugins/indeed-wp-superbackup/ and subdirectories like /uploads/ or /backups/) for unfamiliar PHP files, especially those with random-looking names or recently modified timestamps.Affected if Unknown PHP files exist in the plugin directory or its subdirectories
-
Review WordPress user accounts for unauthorized administratorsIn WordPress admin, go to Users and review all accounts. Look for unfamiliar users with Administrator role, or legitimate admins whose credentials may have been compromised.Affected if There are unexpected admin accounts or suspicious user activity
-
Check for recently created or modified PHP files in the web rootUse file system tools (like find, ls with recent flags, or file manager) to list PHP files created or modified within a timeframe that aligns with the plugin being active, especially in /wp-content/ and subdirectories.Affected if There are unfamiliar PHP files in web-accessible directories that were not intentionally deployed
A user is affected if the WP SuperBackup plugin (indeed-wp-superbackup) version 2.3.3 or earlier is installed and the file upload functionality is accessible to authenticated users.
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 dataUpgrade WP SuperBackup to the latest patched version immediately. If no update is available, disable the plugin and conduct a forensic review of the server for already-uploaded malicious files.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56064 — 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-56064 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