CVE-2020-36667

JetBackup – WP Backup, Migrate & Restore <= 1.4.1 - Missing Authorization to Unauthorized Backup Location Change

2020-07-30 00:00
Chloe Chamberland

Strategic Overview

Status
Patched in 1.4.1
Affected Version
<= 1.4.0
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2020-36667
View all JetBackup – Backup, Restore & Migrate vulnerabilities

At a glance

CVE-2020-36667 is a medium-severity Missing Authorization vulnerability in the JetBackup WordPress plugin, affecting versions <= 1.4.0. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.4.1; sites on affected versions should update now. Disclosed July 2020, reported by Chloe Chamberland.

Vulnerability Overview

The JetBackup – WP Backup, Migrate & Restore plugin for WordPress is vulnerable to unauthorized back-up location changes in versions up to, and including 1.4.1 due to a lack of proper capability checking on the backup_guard_cloud_dropbox, backup_guard_cloud_gdrive, and backup_guard_cloud_oneDrive functions. This makes it possible for authenticated attackers, with minimal permissions, such as a subscriber to change to location of back-ups and potentially steal sensitive information from them.

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

Reaching this weakness in JetBackup <= 1.4.0 takes a caller who can reach the endpoint. 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 JetBackup the fix is 1.4.1: builds <= 1.4.0 are affected, anything from 1.4.1 onward is not.

Remediation

Update to version 1.4.1, 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: JetBackup 1.4.1 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