Backup Migration <= 1.2.9 - Cross-Site Request Forgery

2023-09-05 00:00
Anonymous

Strategic Overview

Status
Patched in 1.3.0
Affected Plugin
Backup Migration
Affected Version
< 1.3.0
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all Backup Migration vulnerabilities

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Backup Migration WordPress plugin, affecting versions < 1.3.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.3.0; sites on affected versions should update now. Disclosed September 2023.

Vulnerability Overview

The Backup Migration plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.2.9. This is due to missing nonce validation on the ajax() function, or BMI_Ajax class. This makes it possible for unauthenticated attackers to control any of the plugin's settings, and restore/delete/modify back-ups via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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.

CWE-352: Cross-Site Request Forgery (CSRF)

Backup Migration < 1.3.0 carries this weakness at ajax(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Backup Migration the fix is 1.3.0: builds < 1.3.0 are affected, anything from 1.3.0 onward is not.

Remediation

Update to version 1.3.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Backup Migration: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Backup Migration 1.3.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/00274313-9079-4877-b72e-310e312aa814

Related records

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