# CVE-2026-18030: Bricksforge < 3.1.8.8 - Unauthenticated Arbitrary Password Reset via Pro Forms

> Unauthenticated attackers can reset passwords for any user, including administrators, via BricksForge Pro Forms, leading to account takeover.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 10 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-3w5j-v478-4p9q

## What is CVE-2026-18030?

CVE-2026-18030 is a high-severity authentication bypass vulnerability in Unknown BricksForge, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The BricksForge WordPress plugin before 3.1.8.8 does not verify the identity of the requester when processing a password change submitted through one of its form actions, allowing unauthenticated attackers to set an arbitrary password for any user, including administrators, and take over their account.

Exploitation requires the site to have a form using the BricksForge WordPress plugin before 3.1.8.8's password reset action in its update mode. The server-side current-password verification option for that action is disabled by default, so the vulnerable state is the default one once the action is used.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-18030 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18030 is a high-severity authentication bypass vulnerability in Unknown BricksForge, published on 10 Aug 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-18030 in the wild and no public exploit code.

Affected product: Unknown 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-18030/ (Markdown: https://insights.sbomify.com/CVE-2026-18030/index.md)
```

## Sources

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

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