Beaver BuilderWordPress extension · Fastlinemedia
CVE-2023-50889
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in The Beaver Builder Team Beaver Builder – WordPress Page Builder allows Stored XSS.This issue affects Beaver Builder – WordPress Page Builder: from n/a through 2.7.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA Stored Cross-Site Scripting (XSS) vulnerability exists in Beaver Builder WordPress Page Builder versions through 2.7.2. The vulnerability stems from improper neutralization of user-supplied input during web page generation, allowing malicious scripts to be stored in the database and executed when other users view compromised pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Beaver BuilderWordPress extension
<= 2.7.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Beaver Builder plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > find 'Beaver Builder Plugin' and read the Version number displayedAffected if The displayed version is 2.7.2 or lower
-
Verify Beaver Builder is activeCheck if the Beaver Builder plugin is enabled on the WordPress site by viewing the Plugins list in the admin dashboardAffected if Beaver Builder plugin is active and version is 2.7.2 or lower
-
Inspect page builder content for injected scriptsReview saved Beaver Builder layouts in the wp_posts database table (post_type: fl-builder-template or fl-builder) or use the WordPress admin to view pages built with Beaver Builder, looking for unexpected script tags or javascript: URLs in text modules, button links, or custom HTML elementsAffected if Any Beaver Builder content contains unsanitized script tags or malicious JavaScript references that were not intentionally added by an administrator
The environment is affected if Beaver Builder version 2.7.2 or lower is installed and active, or if stored malicious scripts exist in Beaver Builder content in the database.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Beaver Builder to the latest available version beyond 2.7.2 where the vulnerability has been patched. Review and sanitize any existing page builder content that may contain injected malicious scripts.
Fix this in Beaver Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50889 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-50889 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data