WP Crowdfunding <= 2.1.10 - Missing Authorization to Authenticated (Subscriber+) to Enable/Disable Addons
Strategic Overview
- Status
- Patched in 2.1.11
- Affected Plugin
- WP Crowdfunding
- Affected Version
<= 2.1.10- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-43937
At a glance
CVE-2024-43937 is a medium-severity Missing Authorization vulnerability in the WP Crowdfunding WordPress plugin, affecting versions <= 2.1.10. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.1.11; sites on affected versions should update now. Disclosed August 2024, reported by Trương Hữu Phúc (truonghuuphuc).
Vulnerability Overview
The WP Crowdfunding plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the addon_enable_disable() function in all versions up to, and including, 2.1.10. This makes it possible for authenticated attackers, with Subscriber-level access and above, to enable/disable addons.
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 interaction from a victim user.
CWE-862: Missing Authorization
WP Crowdfunding <= 2.1.10 carries this weakness at addon_enable_disable(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP Crowdfunding the fix is 2.1.11: builds <= 2.1.10 are affected, anything from 2.1.11 onward is not.
Remediation
Update to version 2.1.11, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Crowdfunding 2.1.11 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 5.3CVE-2025-1508: WP Crowdfunding Authenticated (Subscriber+) Post
CVE-2025-1508 - 4.3CVE-2026-14857: WP Crowdfunding < 2.2.1 Missing Authorization
CVE-2026-14857 - 4.3CVE-2024-11911: WP Crowdfunding Authenticated (Subscriber+)
CVE-2024-11911 - 4.3CVE-2023-41870: WP Crowdfunding <= 2.1.4 Missing Authorization
CVE-2023-41870
Other vulnerabilities in WP Crowdfunding
- 6.4CVE-2026-19945: WP Crowdfunding <= 2.2.1 Stored Cross-Site Scripting
CVE-2026-19945 - 6.4CVE-2025-31892: WP Crowdfunding <= 2.1.15 Stored Cross-Site Scripting
CVE-2025-31892 - 6.4CVE-2024-11910: WP Crowdfunding <= 2.1.15 Stored Cross-Site Scripting
CVE-2024-11910 - 6.4CVE-2024-10117: WP Crowdfunding <= 2.1.11 Stored Cross-Site Scripting
CVE-2024-10117 - 6.4CVE-2023-50859: WP Crowdfunding <= 2.1.6 Stored Cross-Site Scripting
CVE-2023-50859 - 6.1CVE-2023-6161: WP Crowdfunding <= 2.1.8 Reflected Cross-Site Scripting
CVE-2023-6161 - 6.1CVE-2023-47532: WP Crowdfunding <= 2.1.6 Reflected XSS
CVE-2023-47532 - 4.9CVE-2026-19944: WP Crowdfunding <= 2.2.1 SQL Injection
CVE-2026-19944
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C