CVE-2024-1175

WP-Recall – Registration, Profile, Commerce & More <= 16.26.6 - Unauthenticated Payment Deletion via delete_payment

2024-06-05 15:33
Francesco Carlucci

Strategic Overview

Status
Patched in 16.26.7
Affected Plugin
WP-Recall – Registration, Profile, Commerce & More
Affected Version
<= 16.26.6
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-1175
View all WP-Recall – Registration, Profile, Commerce & More vulnerabilities

At a glance

CVE-2024-1175 is a medium-severity Missing Authorization vulnerability in the WP-Recall WordPress plugin, affecting versions <= 16.26.6. It carries a CVSS score of 5.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 Francesco Carlucci.

Vulnerability Overview

The WP-Recall – Registration, Profile, Commerce & More plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'delete_payment' function in all versions up to, and including, 16.26.6. This makes it possible for unauthenticated attackers to delete arbitrary payments.

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

CWE-862: Missing Authorization

WP-Recall <= 16.26.6 carries this weakness at delete_payment, and reaching it takes no account at all. 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 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?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP-Recall 16.26.7 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-1175https://www.wordfence.com/threat-intel/vulnerabilities/id/6b84b13a-b46c-48fc-a7a8-de32c575d576https://nvd.nist.gov/vuln/detail/CVE-2024-1175

Related records

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