CVE-2024-8795

BA Book Everything <= 1.6.20 - Cross-Site Request Forgery to Email Address Update/Account Takeover

2024-09-23 00:00
wesley (wcraft)

Strategic Overview

Status
Patched in 1.6.21
Affected Plugin
BA Book Everything
Affected Version
<= 1.6.20
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-8795
View all BA Book Everything vulnerabilities

At a glance

CVE-2024-8795 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the BA Book Everything WordPress plugin, affecting versions <= 1.6.20. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.6.21; sites on affected versions should update now. Disclosed September 2024, reported by wesley (wcraft).

Vulnerability Overview

The BA Book Everything plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.6.20. This is due to missing or incorrect nonce validation on the my_account_update() function. This makes it possible for unauthenticated attackers to update a user's account details via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. This can be leveraged to reset a user's password and gain access to their account.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

BA Book Everything <= 1.6.20 carries this weakness at my_account_update(), 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 BA Book Everything the fix is 1.6.21: builds <= 1.6.20 are affected, anything from 1.6.21 onward is not.

Remediation

Update to version 1.6.21, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to BA Book Everything: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: BA Book Everything 1.6.21 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