CVE-2026-3143

Total Upkeep <= 1.17.1 - Missing Authorization to Unauthenticated Rollback Cancellation

2026-04-30 00:00
Nabil Irawan

Strategic Overview

Status
Patched in 1.17.2
Affected Version
<= 1.17.1
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-3143
View all Total Upkeep – WordPress Backup Plugin plus Restore & Migrate by BoldGrid vulnerabilities

At a glance

CVE-2026-3143 is a medium-severity Missing Authorization vulnerability in the Total Upkeep WordPress plugin, affecting versions <= 1.17.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.17.2; sites on affected versions should update now. Disclosed April 2026, reported by Nabil Irawan.

Vulnerability Overview

The 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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Total Upkeep <= 1.17.1 carries this weakness at wp_ajax_cli_cancel, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Total Upkeep the fix is 1.17.2: builds <= 1.17.1 are affected, anything from 1.17.2 onward is not.

Remediation

Update to version 1.17.2, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Total Upkeep 1.17.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C