CVE-2024-5076

Wp EMember <= 10.6.5 - Cross-Site Request Forgery to Bulk Delete

2024-06-22 00:00
Bob Matyas

Strategic Overview

Status
Patched in 10.6.6
Affected Plugin
Wp EMember
Affected Version
<= 10.6.5
CVSS
4.3Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2024-5076
View all Wp EMember vulnerabilities

At a glance

CVE-2024-5076 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Wp EMember WordPress plugin, affecting versions <= 10.6.5. 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 10.6.6; sites on affected versions should update now. Disclosed June 2024, reported by Bob Matyas.

Vulnerability Overview

The Wp EMember plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 10.6.5. This is due to missing or incorrect nonce validation on the emember_payments page. This makes it possible for unauthenticated attackers to bulk delete payments 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-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in Wp EMember <= 10.6.5 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Wp EMember the fix is 10.6.6: builds <= 10.6.5 are affected, anything from 10.6.6 onward is not.

Remediation

Update to version 10.6.6, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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