# CVE-2026-11882: Builderall for WordPress < 3.0.2 - Unauthenticated OAuth Access Token Poisoning via Public REST Routes

> Unauthenticated attackers can poison OAuth tokens via public REST routes, potentially overwriting stored integration access tokens on connected sites.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-q7qm-9x83-phwf

## What is CVE-2026-11882?

CVE-2026-11882 is a low-severity authentication bypass vulnerability in Unknown Builderall for WordPress, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Builderall for WordPress plugin before 3.0.2 does not bind the state value of its public OAuth authentication routes to the initiating user session, allowing unauthenticated attackers to complete the connection flow and overwrite the stored third-party integration access token. A durable overwrite requires the site to already be connected to a paid account.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-11882 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11882 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11882 is a low-severity authentication bypass vulnerability in Unknown Builderall for WordPress, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11882 exists.

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

## Sources

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

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