Builderall OAuth state is not bound to the initiating visitor
Builderall for WordPress before 3.0.2 exposes public OAuth routes whose state value is not bound to the browser session that initiated authorization. An unauthenticated attacker can complete a connection flow and replace the access token stored for the site's third-party integration; a durable overwrite requires the site to already be connected to a paid account. The published record does not disclose the routes, state and code parameters, callback function or provider scopes available to the replacement token.
- Component
- Builderall for WordPress
- Plugin slug
builderall-for- Affected
- < 3.0.2
- Safe version
3.0.2- Published
- Aug 01, 2026
- Weakness
- Not assigned
This CVE was published Aug 01, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update Builderall for WordPress to 3.0.2 or later. Reconnect the integration through a trusted administrator session, revoke unexpected or superseded provider tokens, review OAuth callbacks and third-party account activity, and investigate automation changes made with a substituted token.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical 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.