CVE-2026-3143
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 Total Upkeep – WordPress Backup Plugin plus Restore & Migrate by BoldGrid plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'wp_ajax_cli_cancel' function in all versions up to, and including, 1.17.1. This makes it possible for unauthenticated attackers to cancel a pending rollback, potentially preventing a WordPress installation from automatically reverting a failed update.
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 Total Upkeep WordPress backup plugin has a broken access control vulnerability where the 'wp_ajax_cli_cancel' function lacks capability verification, allowing unauthenticated attackers to cancel pending rollback operations via the WordPress AJAX API. This could prevent automated recovery from failed updates.
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 Total Upkeep plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Total Upkeep' or check the plugin files in wp-content/plugins/total-upkeep/ for the main PHP file and read the version headerAffected if Total Upkeep plugin is not installed
-
Check installed plugin versionIn WordPress admin Plugins page, click on the Total Upkeep plugin to view version details, or open the main plugin file (usually total-upkeep.php) and look for 'Version:' in the plugin header commentAffected if Version is present and is below 1.17.2
-
Confirm AJAX endpoint is registeredSearch plugin source files for 'wp_ajax_cli_cancel' action hook registration (wp_ajax_cli_cancel) or check if the function handling this action exists in the plugin codeAffected if The 'wp_ajax_cli_cancel' AJAX action is registered and accessible
-
Test unauthenticated AJAX accessSend a POST request to /wp-admin/admin-ajax.php with action=cli_cancel (no authentication required) using curl or similar toolAffected if The request is processed without requiring authentication (no 401/403 error)
-
Check if rollback functionality is enabledReview Total Upkeep settings in WordPress admin under Total Upkeep > Settings to confirm rollback/backup restore features are configuredAffected if Rollback or automated backup recovery is enabled and configured
User is affected if Total Upkeep plugin is installed with version below 1.17.2 and the wp_ajax_cli_cancel AJAX endpoint accepts unauthenticated requests, allowing attackers to cancel rollback operations.
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 version 1.17.2 or later which adds proper capability checks to the affected AJAX function. Until patched, consider disabling the plugin if rollback functionality is critical.
- 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-2026-3143 — 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-2026-3143 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