CVE-2024-24869

Total Upkeep <= 1.15.8 - Improper Authorization to Unauthenticated Arbitrary File Download

2024-02-02 00:00
beluga

Strategic Overview

Status
Patched in 1.15.9
Affected Version
<= 1.15.8
CVSS
7.5High
Weakness type
CWE-285 · Improper Authorization
CVE
CVE-2024-24869
View all Total Upkeep – WordPress Backup Plugin plus Restore & Migrate by BoldGrid vulnerabilities

At a glance

CVE-2024-24869 is a high-severity Improper Authorization vulnerability in the Total Upkeep WordPress plugin, affecting versions <= 1.15.8. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 1.15.9; sites on affected versions should update now. Disclosed February 2024, reported by beluga.

Vulnerability Overview

The Total Upkeep – WordPress Backup Plugin plus Restore & Migrate by BoldGrid plugin for WordPress is vulnerable to unauthorized access of data due to an improper authorization check in all versions up to, and including, 1.15.8. This makes it possible for unauthenticated attackers to download arbitrary files using the plugin's CLI functionality.

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. A successful exploit has high impact on confidentiality.

CWE-285: Improper Authorization

Reaching this weakness in Total Upkeep <= 1.15.8 takes no account at all. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.

A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For Total Upkeep the fix is 1.15.9: builds <= 1.15.8 are affected, anything from 1.15.9 onward is not.

Remediation

Update to version 1.15.9, 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.15.9 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