Authentication Bypass Using an Alternate Path or Channel (CWE-288)
The WordPress & WooCommerce Affiliate Program plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 8.4.1. This vulnerability is caused by the rtwwwap_login_request_callback() function not properly validating a user's identity before authenticating them to the site. As a result, unauthenticated attackers can potentially log in as any user, including administrators, if they have access to the administrator's email.
This vulnerability has severe implications for affected WordPress sites using the WordPress & WooCommerce Affiliate Program plugin. Attackers exploiting this vulnerability could gain unauthorized access to user accounts, including those with administrative privileges. This could lead to complete compromise of the affected WordPress site, allowing attackers to: 1. Access and modify sensitive information 2. Install or remove plugins and themes 3. Add, modify, or delete content 4. Access and potentially exfiltrate user data 5. Use the compromised site for further malicious activities, such as hosting malware or conducting phishing campaigns The potential for administrative access makes this vulnerability particularly dangerous, as it could result in full site takeover.
There is no evidence that a public proof-of-concept exists. There is no evidence of proof of exploitation at the moment.
A patch is not explicitly mentioned in the provided information. However, given that the vulnerability affects "all versions up to, and including, 8.4.1" of the WordPress & WooCommerce Affiliate Program plugin, it is likely that a patched version (8.4.2 or higher) may be available or in development. Site administrators should check for updates to the plugin and apply them as soon as they become available.
While waiting for an official patch, consider the following mitigation strategies: 1. Temporarily disable the WordPress & WooCommerce Affiliate Program plugin if it's not critical to your operations. 2. Implement strong access controls and monitor for any suspicious login activities, especially those associated with administrative accounts. 3. Use two-factor authentication for all user accounts, particularly for administrative users. 4. Regularly audit user accounts and remove any unnecessary administrative privileges. 5. Keep WordPress core, all themes, and other plugins up to date. 6. Implement Web Application Firewall (WAF) rules to detect and block potential exploitation attempts targeting the vulnerable function. 7. Monitor for any unauthorized changes to your WordPress site's content or configuration. 8. Regularly backup your WordPress site and ensure you have a tested restoration process in place. Once a patch becomes available, apply it immediately after testing in a staging environment.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD published the first details for CVE-2024-9289
Feedly found the first article mentioning CVE-2024-9289. See article
A CVSS base score of 9.8 has been assigned.
Feedly estimated the CVSS score as HIGH
EPSS Score was set to: 0.09% (Percentile: 39.7%)