CVE-2026-11882: CWE-284 Improper Access Control in Builderall for WordPress
Builderall for WordPress plugin versions before 3.0.2 contain an improper access control vulnerability in their public OAuth authentication routes. The plugin does not bind the OAuth state value to the initiating user session, which allows unauthenticated attackers to complete the OAuth connection flow and overwrite stored third-party integration access tokens. A persistent overwrite requires the site to already be connected to a paid Builderall account.
AI Analysis
Technical Summary
CVE-2026-11882 is an improper access control vulnerability (CWE-284) in the Builderall for WordPress plugin prior to version 3.0.2. The issue arises because the plugin's public OAuth authentication routes fail to bind the state parameter to the user session that initiated the OAuth flow. This flaw enables unauthenticated attackers to finalize the OAuth connection process and overwrite the stored access token for third-party integrations. For the overwrite to be durable, the targeted site must already have an active connection to a paid Builderall account. No CVSS score or known exploits in the wild are currently reported.
Potential Impact
An attacker can unauthenticatedly manipulate the OAuth connection process to overwrite stored third-party integration access tokens. This could potentially disrupt integrations relying on these tokens or allow unauthorized access via the overwritten tokens. However, a persistent impact requires the site to be connected to a paid Builderall account, limiting the scope of exploitation. There is no evidence of active exploitation in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch is documented, users should monitor for updates from the Builderall plugin vendor and apply any released updates promptly. Until a fix is available, consider restricting access to the OAuth authentication routes or implementing additional access controls if feasible.
CVE-2026-11882: CWE-284 Improper Access Control in Builderall for WordPress
Description
Builderall for WordPress plugin versions before 3.0.2 contain an improper access control vulnerability in their public OAuth authentication routes. The plugin does not bind the OAuth state value to the initiating user session, which allows unauthenticated attackers to complete the OAuth connection flow and overwrite stored third-party integration access tokens. A persistent overwrite requires the site to already be connected to a paid Builderall account.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-11882 is an improper access control vulnerability (CWE-284) in the Builderall for WordPress plugin prior to version 3.0.2. The issue arises because the plugin's public OAuth authentication routes fail to bind the state parameter to the user session that initiated the OAuth flow. This flaw enables unauthenticated attackers to finalize the OAuth connection process and overwrite the stored access token for third-party integrations. For the overwrite to be durable, the targeted site must already have an active connection to a paid Builderall account. No CVSS score or known exploits in the wild are currently reported.
Potential Impact
An attacker can unauthenticatedly manipulate the OAuth connection process to overwrite stored third-party integration access tokens. This could potentially disrupt integrations relying on these tokens or allow unauthorized access via the overwritten tokens. However, a persistent impact requires the site to be connected to a paid Builderall account, limiting the scope of exploitation. There is no evidence of active exploitation in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch is documented, users should monitor for updates from the Builderall plugin vendor and apply any released updates promptly. Until a fix is available, consider restricting access to the OAuth authentication routes or implementing additional access controls if feasible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- WPScan
- Date Reserved
- 2026-06-10T13:30:47.525Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6d96cfbf32cb7a344cecbc
Added to database: 08/01/2026, 06:48:47 UTC
Last enriched: 08/01/2026, 07:23:12 UTC
Last updated: 08/01/2026, 08:06:17 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.