Clone <= 2.3.7 - Cross-Site Request Forgery via wp_ajax_tifm_save_decision

2023-03-08 00:00
Kévin Mosbahi (Mika)

Strategic Overview

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

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Clone WordPress plugin, affecting versions <= 2.3.7. 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 2.3.8; sites on affected versions should update now. Disclosed March 2023, reported by Kévin Mosbahi (Mika).

Vulnerability Overview

The Clone plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.3.7. This is due to missing or incorrect nonce validation on the wp_ajax_tifm_save_decision function. This makes it possible for unauthenticated attackers to modify the 'Test new plugins before installing' setting 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)

Reaching this weakness in Clone <= 2.3.7 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 Clone the fix is 2.3.8: builds <= 2.3.7 are affected, anything from 2.3.8 onward is not.

Remediation

Update to version 2.3.8, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/314d3e0c-ba29-4795-a646-40e0acfc3405

Related records

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