CVE-2024-8795
Cross-Site Request Forgery (CSRF) (CWE-352)
Summary
The BA Book Everything plugin for WordPress contains a Cross-Site Request Forgery (CSRF) vulnerability in all versions up to and including 1.6.20. This vulnerability stems from missing or incorrect nonce validation in the my_account_update() function. As a result, unauthenticated attackers can potentially update a user's account details through a forged request, provided they can deceive a site administrator into performing an action such as clicking on a malicious link.
Impact
The impact of this vulnerability is severe, with a CVSS v3.1 base score of 8.8 (High). Successful exploitation could lead to: 1. Unauthorized account access: Attackers can reset a user's password, potentially gaining full access to their account. 2. Data breach: With access to user accounts, sensitive information could be compromised. 3. Privilege escalation: If an attacker gains access to an administrator account, they could potentially take control of the entire WordPress site. 4. Reputational damage: Compromised user accounts could lead to loss of trust in the website or organization. It's important to note that while the attack requires user interaction (such as an administrator clicking a malicious link), it can be executed by an unauthenticated attacker from the network, increasing its potential reach and severity.
Exploitation
There is no evidence that a public proof-of-concept exists. There is no evidence of proof of exploitation at the moment.
Patch
A patch is available for this vulnerability. The issue has been addressed in version 1.6.21 of the BA Book Everything plugin for WordPress. Website administrators should update to this version or later as soon as possible to mitigate the risk.
Mitigation
To mitigate this vulnerability, consider the following recommendations: 1. Update immediately: Upgrade the BA Book Everything plugin to version 1.6.21 or later. 2. Implement strong authentication: Use multi-factor authentication for administrator accounts to reduce the risk of unauthorized access. 3. User awareness: Educate administrators and users about the risks of clicking on suspicious links, especially when logged into the WordPress dashboard. 4. Regular security audits: Conduct periodic reviews of installed plugins and their versions to ensure they are up-to-date and free from known vulnerabilities. 5. Web Application Firewall (WAF): Consider implementing a WAF that can help detect and block CSRF attacks. 6. Principle of least privilege: Ensure that user accounts have only the necessary permissions required for their roles. Given the high severity score and the potential for significant impact, addressing this vulnerability should be prioritized in your patching and remediation efforts.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Timeline
NVD published the first details for CVE-2024-8795
Feedly found the first article mentioning CVE-2024-8795. See article
Feedly estimated the CVSS score as LOW
Feedly estimated the CVSS score as MEDIUM
Detection for the vulnerability has been added to Qualys (152231)
EPSS Score was set to: 0.05% (Percentile: 22.7%)