CVE-2024-5077

Wp EMember <= 10.6.5 - Cross-Site Request Forgery

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
6.1Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-5077
View all Wp EMember vulnerabilities

At a glance

CVE-2024-5077 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Wp EMember WordPress plugin, affecting versions <= 10.6.5. It carries a CVSS score of 6.1 (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 manage_blacklist() function. This makes it possible for unauthenticated attackers to inject malicious web scripts and update the blacklist 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)

Wp EMember <= 10.6.5 carries this weakness at manage_blacklist(), 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 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

https://www.cve.org/CVERecord?id=CVE-2024-5077https://www.wordfence.com/threat-intel/vulnerabilities/id/d22134ec-00ca-4672-b9b1-1b1efad13aebhttps://nvd.nist.gov/vuln/detail/CVE-2024-5077

Related records

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