CVE-2026-17090: Beaver Builder Page Builder (WordPress plugin) · Cross-site Scripting
Affects Beaver Builder Page Builder (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.4 Medium.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| beaverbuilderBeaver Builder Page Builder – Drag and Drop Website Builder | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, restrict author-level user privileges where possible and monitor for suspicious activity related to page content modifications. Avoid granting edit_posts capability to untrusted users. Follow vendor updates closely for any released patches or official mitigations.
Description
The Beaver Builder Page Builder – Drag and Drop Website Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Button Module 'button' (Button Code) Setting in all versions up to, and including, 2.10.2.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Beaver Builder grants editor access to any WordPress role holding the edit_posts capability by default, meaning Author-level users and above can exploit this vulnerability.
References
- wordfence.com/threat-intel/vulnerabilities/id/0abbdf2c-b1f8-4431-b892-1d7972749af6?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/beaver-builder-lite-version/trunk/modules/button/includes/frontend.js.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/beaver-builder-lite-version/tags/2.10.2.2/modules/button/includes/frontend.js.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/beaver-builder-lite-version/tags/2.10.2.2/classes/class-fl-builder-model.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/beaver-builder-lite-version/tags/2.10.2.2/modules/button/button.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/beaver-builder-lite-version/tags/2.10.1.5/modules/button/includes/frontend.js.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/beaver-builder-lite-version/tags/2.10.1.5/classes/class-fl-builder-model.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/beaver-builder-lite-version/tags/2.10.1.5/modules/button/button.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3645274%40beaver-builder-lite-version&new=3645274%40beaver-builder-lite-version (opens in a new tab)