WP Fusion (Pro) <= 3.47.13 - Authenticated (Subscriber+) Privilege Escalation via ThriveCart Auto Login 'role' Parameter
Strategic Overview
- Status
- Patched in 3.47.14
- Affected Plugin
- WP Fusion (Pro)
- Affected Version
<= 3.47.13- CVSS
- 7.5High
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2026-14444
At a glance
CVE-2026-14444 is a high-severity Improper Privilege Management vulnerability in the WP Fusion (Pro) WordPress plugin, affecting versions <= 3.47.13. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.47.14; sites on affected versions should update now. Disclosed September 2026, reported by Jarno Vos (jarnovos).
Vulnerability Overview
The WP Fusion (Pro) plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.47.13. This is due to insufficient authorization checks on the role parameter in the ThriveCart Auto Login handler's thrivecart() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, and who possess the access_key, to create a new user account with administrator privileges and gain full control over the WordPress site. The required access_key is intentionally shared with ThriveCart customers as part of the plugin's documented setup process, making it accessible to attackers who have made a purchase. The vulnerability is only exploitable when the ThriveCart Auto Login option is enabled.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-269: Improper Privilege Management
WP Fusion (Pro) <= 3.47.13 carries this weakness at thrivecart(), and reaching it takes an account at Subscriber level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For WP Fusion (Pro) the fix is 3.47.14: builds <= 3.47.13 are affected, anything from 3.47.14 onward is not.
Remediation
Update to version 3.47.14, 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 Fusion (Pro) 3.47.14 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C