Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit comment with malicious shortcode
-
DeliveryComment auto-approved or moderation disabled
-
ExploitSidebar Recent Comments widget renders text
-
ExecutionUnvalidated do_shortcode executes payload
-
ImpactArbitrary shortcode execution on page
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation is gated on a specific configuration: the target must publish a Beaver Builder page containing the Sidebar module populated with a widget that renders attacker-controllable text - the description names the core Recent Comments widget - AND comment moderation must be disabled (comments auto-approved) or the attacker's comment must be approved by a moderator. Limiting factors: this is a non-default content/layout combination the attacker cannot guarantee, and reliance on comment approval introduces either an auto-approval misconfiguration or human-in-the-loop interaction. Where present, the attack itself needs no authentication (PR:N) and no victim UI interaction, but the dependency on site-controlled configuration substantially narrows exploitable targets. |
| Impact | The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) scores 9.1 and portrays an unauthenticated, low-complexity, remote code-injection flaw (CWE-94) - normally an urgent priority. However, the description materially qualifies this: successful exploitation requires a specific non-default deployment (a Beaver Builder page rendering the Sidebar module populated with a widget that echoes attacker-controllable text, e.g. the core Recent Comments widget) AND that comment moderation be disabled or the attacker's comment approved. That precondition conflicts with the AC:L rating - the real-world attack complexity is closer to AC:H because the attacker depends on site configuration they do not control. No EPSS score, SSVC decision, KEV listing, or POC is provided in the input, so there is no evidence of active exploitation or published exploit code; exploitation status is therefore 'no public exploit identified at time of analysis.' Net assessment: a genuinely serious bug in a popular plugin, but the configuration dependency makes it more conditional/targeted than the 9.1 implies - triage as high but not drop-everything, and confirm whether affected sites actually expose the vulnerable Sidebar/widget combination. |
| Exploit ScenarioDerived | An unauthenticated attacker submits a blog comment containing a WordPress shortcode payload on a site running a vulnerable Beaver Builder version. If the site auto-approves comments (or the comment is later approved) and a Beaver Builder page renders the Sidebar module with the Recent Comments widget, the plugin passes the comment text through do_shortcode without validation, executing the attacker's shortcode in the page context. No public POC is identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 03, 2026
Arbitrary shortcode execution in the Beaver Builder Page Builder - Drag and Drop Website Builder plugin for WordPress (all versions up to and including 2.11.0.5) lets unauthenticated attackers run attacker-chosen shortcodes on a target site, which in a typical WordPress install with shortcode-extending plugins can escalate to code injection and full site compromise (CWE-94). Exploitation is not automatic: it is gated on the site publishing a Beaver Builder page whose Sidebar module contains a widget rendering attacker-controllable text - the advisory names the core Recent Comments widget - and on either comments being auto-approved (moderation disabled) or the attacker's comment having been approved by a moderator, which makes this a content- and configuration-dependent attack rather than a universally reachable one; the flaws assessed vector therefore carries AC:H rather than the initial AC:L. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor advisory (Wordfence threat ID 794e6d9b-ac07-4261-a60d-81c474973005, mirrored as ENISA EUVD-2026-91966) is the authoritative source for patch rollout.
RemediationAI
No vendor-tagged fixed release was independently confirmed at time of analysis: the only remediation artifact in the reference set is an upstream trunk changeset (https://plugins.trac.wordpress.org/changeset/3713226/beaver-builder-lite-version/trunk/modules/sidebar/sidebar.php) that modifies the Sidebar module, i.e. upstream fix available (changeset/commit); released patched version not independently confirmed. Treat the plugin update channel as the primary fix path and upgrade past 2.11.0.5 as soon as the vendor ships (or has shipped) a release containing changeset 3713226, verifying the installed version after the update since auto-update may be disabled. If upgrading is not immediately possible, apply the following compensating controls in order of effectiveness: (1) enable comment moderation so no comment is published without approval and disable the 'comment author must have a previously approved comment' auto-approval path - trade-off is moderator workload and delayed comment display; (2) audit Beaver Builder layouts and remove the Sidebar module from any page whose widget renders user-controllable text (notably Recent Comments), substituting a static widget or a non-user-populated one - trade-off is loss of dynamic sidebar content on those pages; (3) close comments on pages that include the Sidebar module or restrict comment submission to authenticated, trusted roles - trade-off is reduced engagement; (4) audit existing published comments for shortcode syntax such as bracketed tags with attributes and remove suspicious entries, since the payload persists in stored comment content. Generic WAF signature matching on shortcode payloads is unreliable because shortcode syntax is ordinary content and false positives are frequent, so it should be treated only as a stopgap. Verify the fix against the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/794e6d9b-ac07-4261-a60d-81c474973005?source=cve and note that no vendor patch version number can be stated with confidence from the available data.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-94 (Improper Control of Generation of Code / Code Injection) rooted in the plugin's failure to validate a value before passing it to WordPress's do_shortcode(). Beaver Builder renders its Sidebar module through modules/sidebar/sidebar.php and modules/sidebar/includes/frontend.php, and the module rendering path (classes/class-fl-builder-module.php and the do_shortcode call around classes/class-fl-builder.php line 2139, with a related path near line 2264) processes widget output as shortcode-bearing content. Because core widgets such as Recent Comments output comment author names and comment text nearly verbatim, a commenter controls a string that later lands in a do_shortcode() evaluation context; any registered shortcode - including shortcodes added by other installed plugins that perform file reads, option writes, or PHP evaluation - can then be invoked with attacker-supplied attributes. This is why the impact is rated C:H/I:H: arbitrary shortcode execution is a well-known WordPress privilege-escalation primitive that often converts to remote code execution or persistent site takeover depending on the shortcode surface present. The affected CPE (cpe:2.3:a:beaverbuilder:beaver_builder_page_builder_-_drag_and_drop_website_builder:*:*:*:*:*:*:*:*) covers the Lite distribution, and the advisory's reference set is entirely composed of plugin Trac source snapshots at tag 2.11.0.5 plus a trunk changeset, confirming the flaw is code-level in the plugin itself rather than in WordPress core.
Know when Beaver Builder Page Builder Drag And Drop Website Builder gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Unauthenticated remote (AV:N/PR:N) but exploitation depends on a non-default Sidebar/Recent-Comments configuration and comment approval the attacker cannot control, so AC:H; shortcode execution yields high confidentiality and integrity impact, no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The The Beaver Builder Page Builder - Drag and Drop Website Builder plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 2.11.0.5. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes. Exploitation requires the target site to have a Beaver Builder page containing the Sidebar module populated with a widget that displays attacker-controllable text, such as the core Recent Comments widget, with comment moderation disabled or the attacker's comment approved.
Articles & Coverage 1
Executive ViewAI
Any WordPress site running the Beaver Builder Page Builder plugin at version 2.11.0.5 or earlier is exposed to a critical flaw that could let an outside party execute attacker-controlled code and take full control of the website, including its content, customer-facing pages, and underlying hosting environment. Exploitation is not automatic and depends on specific site configuration and content conditions, and no public exploit code or confirmed active exploitation has been identified at time of analysis, but no vendor fix is currently available for a plugin in wide use. Leadership should treat this as a near-term operational risk that warrants immediate configuration hardening and heightened monitoring of all public-facing WordPress properties.
No vendor-released patch identified at time of analysis. Interim mitigations: disable comment auto-approval and require manual moderation of all comments; disable comments on Beaver Builder pages; remove the Recent Comments widget and any other visitor-controllable widget from Beaver Builder Sidebar modules; block shortcode execution from user-supplied content via a security plugin or custom filter; deploy WAF/virtual-patching rules targeting shortcode payloads in comment fields; and deactivate or remove the Beaver Builder plugin entirely if it is not business-essential.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Blind SQL injection in the Beaver Builder Page Builder plugin for WordPress (versions up to and including 2.11.0.5) allo
Arbitrary shortcode execution in Beaver Builder Page Builder for WordPress (all versions ≤2.10.3.1) allows unauthenticat
Stored Cross-Site Scripting in Beaver Builder Page Builder for WordPress (all versions up to and including 2.10.2.2) all
Stored Cross-Site Scripting in Beaver Builder Page Builder plugin for WordPress up to version 2.10.1.1 allows authentica
EUVD-2026-91966
GHSA-jx8c-663q-ggc5
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB