# CVE-2026-14956: Bricksforge <= 3.1.8.6 - Unauthenticated Privilege Escalation via Pro Forms fieldIds Parameter

> Unauthenticated attackers can escalate privileges to administrator by exploiting improper validation in Bricksforge Pro Forms registration.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-3h83-c8w5-cccx

## What is CVE-2026-14956?

CVE-2026-14956 is a critical vulnerability in Bricksforge, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-14956?


## How do I fix CVE-2026-14956?

No fix has been published for CVE-2026-14956 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14956 being exploited?

There is no known exploitation of CVE-2026-14956 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14956 and fix it if it is affected.

What it is: CVE-2026-14956 is a critical vulnerability in Bricksforge, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14956 in the wild and no public exploit code.

Affected product: Bricksforge. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14956/ (Markdown: https://insights.sbomify.com/CVE-2026-14956/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14956
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14956
- OSV: https://osv.dev/vulnerability/CVE-2026-14956

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14956/
Summaries are generated and may contain mistakes; the official description above is the record.