Thrive Theme Builder < 3.24.2 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 3.24.2
- Affected Theme
- Thrive Themes Builder
- Affected Version
< 3.24.2- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-47781
At a glance
CVE-2023-47781 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Thrive Themes Builder WordPress theme, affecting versions < 3.24.2. 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 3.24.2; sites on affected versions should update now. Disclosed November 2023, reported by Rafie Muhammad.
Vulnerability Overview
The Thrive Theme Builder theme for WordPress is vulnerable to Cross-Site Request Forgery in all versions prior to 3.24.2. This is due to missing or incorrect nonce validation on the affected function. This makes it possible for unauthenticated attackers to invoke this function 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Thrive Themes Builder < 3.24.2 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 Thrive Themes Builder the fix is 3.24.2: builds < 3.24.2 are affected, anything from 3.24.2 onward is not.
Remediation
Update to version 3.24.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Thrive Themes Builder: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Thrive Themes Builder 3.24.2 closes this, and updating the theme is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C