CVE-2022-4932

Total Upkeep <= 1.14.13 - Missing Authorization to Authenticated (Subscriber+) Information Disclosure

2022-02-24 00:00
Chloe Chamberland

Strategic Overview

Status
Patched in 1.14.14
Affected Plugin
Total Upkeep – WordPress Backup Plugin plus Restore & Migrate by BoldGrid
Affected Version
<= 1.14.13
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-4932
View all Total Upkeep – WordPress Backup Plugin plus Restore & Migrate by BoldGrid vulnerabilities

At a glance

CVE-2022-4932 is a medium-severity Missing Authorization vulnerability in the Total Upkeep WordPress plugin, affecting versions <= 1.14.13. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.14.14; sites on affected versions should update now. Disclosed February 2022, reported by Chloe Chamberland.

Vulnerability Overview

The Total Upkeep plugin for WordPress is vulnerable to information disclosure in versions up to, and including 1.14.13. This is due to missing authorization on the heartbeat_received() function that triggers on WordPress heartbeat. This makes it possible for authenticated attackers, with subscriber-level permissions and above to retrieve back-up paths that can subsequently be used to download the back-up.

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 interaction from a victim user.

CWE-862: Missing Authorization

Total Upkeep <= 1.14.13 carries this weakness at heartbeat_received(), and reaching it takes an account at Subscriber level or above. 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.14.14: builds <= 1.14.13 are affected, anything from 1.14.14 onward is not.

Remediation

Update to version 1.14.14, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Total Upkeep 1.14.14 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-4932https://www.wordfence.com/threat-intel/vulnerabilities/id/0e346146-1c00-4e03-a6c7-372566d7ffc9https://nvd.nist.gov/vuln/detail/CVE-2022-4932

Related records

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