Strategic Overview
- Status
- Patched in 1.8.8
- Affected Plugin
- Patreon WordPress
- Affected Version
<= 1.8.7- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-41129
At a glance
CVE-2023-41129 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Patreon WordPress WordPress plugin, affecting versions <= 1.8.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.8.8; sites on affected versions should update now. Disclosed November 2023, reported by BuShiYue.
Vulnerability Overview
The Patreon WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.8.7. This is due to missing or incorrect nonce validation on several functions in the ~/classes/patreon_wordpress.php file. This makes it possible for unauthenticated attackers to modify the plugin's settings among other actions 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)
Reaching this weakness in Patreon WordPress <= 1.8.7 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 Patreon WordPress the fix is 1.8.8: builds <= 1.8.7 are affected, anything from 1.8.8 onward is not.
Remediation
Update to version 1.8.8, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Patreon WordPress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Patreon WordPress 1.8.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Patreon WordPress
- 9.8CVE-2018-20984: Patreon WordPress < 1.2.2 PHP Object Injection
CVE-2018-20984 - 9.6CVE-2021-24228: Patreon WordPress <= 1.7.0 Reflected XSS
CVE-2021-24228 - 9.6CVE-2021-24229: Patreon WordPress <= 1.7.0 Reflected XSS
CVE-2021-24229 - 7.5CVE-2021-24227: Patreon WordPress < 1.7.0 Local File Disclosure
CVE-2021-24227 - 5.5CVE-2021-25026: Patreon WordPress <= 1.8.1 Stored Cross-Site Scripting
CVE-2021-25026 - 5.3CVE-2025-24588: Patreon WordPress <= 1.9.1 Missing Authorization
CVE-2025-24588 - 5.3CVE-2024-37430: Patreon WordPress <= 1.9.0 Protection Mechanism Bypass
CVE-2024-37430
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C