Bricksforge <= 3.1.8.6 - Unauthenticated Privilege Escalation via Pro Forms fieldIds Parameter
Strategic Overview
- Status
- Patched in 3.1.8.7
- Affected Plugin
- Bricksforge
- Affected Version
<= 3.1.8.6- CVSS
- 9.8Critical
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2026-14956
At a glance
CVE-2026-14956 is a critical-severity Improper Privilege Management vulnerability in the Bricksforge WordPress plugin, affecting versions <= 3.1.8.6. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.1.8.7; sites on affected versions should update now. Disclosed July 2026, reported by 0xd4rk5id3.
Vulnerability Overview
The Bricksforge plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.1.8.6. This is due to improper validation of the fieldIds parameter in the Pro Forms registration action, which allows attacker-supplied field IDs to be added to the trusted form-field whitelist. This makes it possible for unauthenticated attackers to register a new administrator account by submitting a crafted request to a publicly accessible Bricksforge Pro Forms registration form. Successful exploitation requires that the site has a public Bricksforge Pro Forms element configured with the User Registration action.
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, 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 Bricksforge <= 3.1.8.6 takes no account at all. 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 Bricksforge the fix is 3.1.8.7: builds <= 3.1.8.6 are affected, anything from 3.1.8.7 onward is not.
Remediation
Update to version 3.1.8.7, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Bricksforge 3.1.8.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Bricksforge
- 5.3CVE-2026-34888: Bricksforge <= 3.1.8.4 Information Exposure
CVE-2026-34888 - 5.3CVE-2024-31242: Bricksforge Unauthenticated Arbitrary Email Sending
CVE-2024-31242 - 5.3CVE-2024-31244: Bricksforge Unauthenticated WordPress Settings Update
CVE-2024-31244 - 5.3CVE-2024-31243: Bricksforge Unauthenticated WordPress Settings
CVE-2024-31243
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C