CVE-2024-35657

WP-Recall <= 16.26.6 - Cross-Site Request Forgery

2024-06-03 00:00
Steven Julian

Strategic Overview

Status
Patched in 16.26.7
Affected Plugin
WP-Recall – Registration, Profile, Commerce & More
Affected Version
<= 16.26.6
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-35657
View all WP-Recall – Registration, Profile, Commerce & More vulnerabilities

At a glance

CVE-2024-35657 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP-Recall WordPress plugin, affecting versions <= 16.26.6. 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 16.26.7; sites on affected versions should update now. Disclosed June 2024, reported by Steven Julian.

Vulnerability Overview

The WP-Recall plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 16.26.6. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action 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 WP-Recall <= 16.26.6 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 WP-Recall the fix is 16.26.7: builds <= 16.26.6 are affected, anything from 16.26.7 onward is not.

Remediation

Update to version 16.26.7, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-35657https://www.wordfence.com/threat-intel/vulnerabilities/id/dc8704f2-01ee-4193-ae8d-96a7f5383d21https://nvd.nist.gov/vuln/detail/CVE-2024-35657

Related records

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