CVE-2024-43270
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 · uneditedMissing Authorization vulnerability in WPBackItUp Backup and Restore WordPress allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Backup and Restore WordPress: from n/a through 1.50.
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 · moderate confidenceMissing authorization vulnerability in the WPBackItUp Backup and Restore WordPress plugin allows access to functionality that is not properly constrained by Access Control Lists (ACLs), potentially enabling unauthorized users to access sensitive backup and restore operations.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 WPBackItUp plugin is installedLog into WordPress admin and navigate to Plugins > Installed Plugins, or check for the wp-content/plugins/wpbackitup folder via file system inspectionAffected if The WPBackItUp plugin appears in the list of active or installed plugins
-
Identify the installed WPBackItUp versionIn WordPress admin, view the plugin details page to see the version number, or open the main plugin PHP file and look for the version header commentAffected if The displayed version matches any version known to contain this authorization bypass vulnerability
-
Confirm plugin endpoints are accessible without proper authenticationTest accessing WPBackItUp AJAX endpoints or admin pages directly via curl or browser while logged out or as a low-privilege user (e.g., curl -I https://your-site.com/wp-admin/admin-ajax.php?action=wpbackitup_*)Affected if Requests return successful HTTP responses or expose backup/restore functionality rather than redirecting to login or returning 403 Forbidden
-
Check for missing capability checks on plugin actionsReview the plugin source code (wp-content/plugins/wpbackitup/) for functions that handle backup creation, restoration, or file downloads and verify if they include current_user_can() or capability checks before executingAffected if Backup, restore, or download functions lack proper capability verification and execute for unauthenticated or unauthorized users
Your environment is affected if the WPBackItUp plugin is installed and its backup/restore functions can be accessed by users lacking WordPress administrator privileges, indicating the ACL bypass is present.
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 to the latest patched version of WPBackItUp when available; alternatively, restrict access to the plugin's admin functionality using server-level authentication requirements or a WAF to enforce authorization checks.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43270 — 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-43270 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