Crowdfundly <= 2.2.2 - Authenticated (Crowdfundly Manager+) Privilege Escalation
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Crowdfundly
- Affected Version
<= 2.2.2- CVSS
- 8.8High
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2026-85126
At a glance
CVE-2026-85126 is a high-severity Improper Privilege Management vulnerability in the Crowdfundly WordPress plugin, affecting versions <= 2.2.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Crowdfundly Manager level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2026, reported by Enrico Marcolini.
Vulnerability Overview
The Crowdfundly plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.2.2. This is due to insufficient restriction on the capabilities a user may grant themselves. This makes it possible for authenticated attackers, with crowdfundly manager-level access and above, to elevate their privileges beyond those intended for their role.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-269: Improper Privilege Management
Reaching this weakness in Crowdfundly <= 2.2.2 takes an account at Crowdfundly Manager 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. No fixed build of this plugin is recorded for Crowdfundly yet, so installs running <= 2.2.2 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C