CVE-2026-14956: Bricksforge <= 3.1.8.6 - Unauthenticated Privilege Escalation via Pro Forms fieldIds Parameter
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-14956 lets an unauthenticated visitor create an administrator account on vulnerable WordPress sites using Bricksforge Pro Forms registration. The risk is critical because compromise can lead to full site takeover. Exposure depends on both plugin version and whether a public Pro Forms registration form with User Registration is enabled.
Executive priority
Treat this as urgent for any public WordPress site using Bricksforge registration forms. The business impact is potential site takeover without login credentials. Prioritize inventory, temporary form disablement, vendor update tracking, and administrator account review.
Technical view
Bricksforge for WordPress through 3.1.8.6 improperly validates the Pro Forms registration fieldIds parameter. Attacker-supplied field IDs can enter a trusted field whitelist, enabling unauthorized administrator account creation. The CVSS 3.1 score is 9.8, with network attack vector, low complexity, no privileges, and no user interaction.
Likely exposure
Likely exposed systems are WordPress sites running Bricksforge up to and including 3.1.8.6 with a publicly accessible Bricksforge Pro Forms element configured for User Registration. The provided source metadata is partly inconsistent, so confirm installed plugin versions directly.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The condition for exploitation is specific: a public Bricksforge Pro Forms registration form using the User Registration action must exist. No exploit procedure is needed to understand the business risk.
Researcher notes
Evidence supports a critical privilege escalation in Bricksforge through 3.1.8.6. The CVE affected-product block in the provided bundle appears incomplete or inconsistent with the narrative description. Do not assume exploitation in the wild from this bundle alone; KEV is false.
Mitigation direction
Inventory WordPress sites using the Bricksforge plugin.
Check Bricksforge vendor guidance and changelog for a fixed release.
Update Bricksforge once a fixed version is confirmed by the vendor.
Disable public Pro Forms User Registration until remediation is complete.
Review recent administrator accounts for unauthorized additions.
Restrict or remove unnecessary public registration workflows.
Validation and detection
Confirm installed Bricksforge versions across WordPress environments.
Identify public Bricksforge Pro Forms using User Registration.
Review WordPress admin users created since exposure began.
Check web and application logs for suspicious registration activity.
Verify remediation by confirming vulnerable forms are removed or patched.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-269 · source CWE mapping
Improper Privilege Management
Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.