dbcve.org
Beaver BuilderWordPress extension · Fastlinemedia

CVE-2022-2517

MEDIUM · 5.4 CVSS v3.1 Published 2022-09-06
Fix available
A fix is available. Upgrade to after 2.5.5.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
The Beaver Builder – WordPress Page Builder for WordPress is vulnerable to Stored Cross-Site Scripting via the 'Caption - On Hover' value associated with images in versions up to, and including, 2.5.5.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers with access to the Beaver Builder editor to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 · high confidence

The Beaver Builder plugin for WordPress suffers from a stored XSS vulnerability in the image 'Caption - On Hover' field. Authenticated users with Beaver Builder editor access can inject malicious JavaScript via insufficiently sanitized input, which then executes when other users access the affected pages.

MitigationUpdate Beaver Builder to a version newer than 2.5.5.2. Until patched, restrict editor access to only highly trusted users and consider deploying a WAF to help detect XSS exploitation attempts.

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
Affected:<= 2.5.5.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Beaver Builder is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Beaver Builder Plugin' (Fastlinemedia)
    Affected if Plugin is not installed or not present in the plugins list
  2. Check installed Beaver Builder version
    In WordPress admin, go to Plugins > Installed Plugins, find Beaver Builder, and note the version number displayed under the plugin name
    Affected if Version is 2.5.5.2 or lower (any version up to and including 2.5.5.2)
  3. Identify pages using the Caption - On Hover feature
    In WordPress admin with Beaver Builder active, open the Beaver Builder editor on any page/post. Add an image module and check if the 'Caption - On Hover' field is available in the image settings panel
    Affected if The Caption - On Hover field is present and accessible in the Beaver Builder editor interface
  4. Inspect image caption data for malicious scripts
    Access your WordPress database (via phpMyAdmin or CLI) and query the wp_posts table for any content containing caption fields with script tags or javascript: URIs. Example SQL: SELECT * FROM wp_posts WHERE post_content LIKE '%caption%on%hover%' OR post_content LIKE '%<script%';
    Affected if Any image caption entries contain <script> tags, javascript: event handlers, or other XSS payloads in the database

You are affected if Beaver Builder version 2.5.5.2 or lower is installed AND the Caption - On Hover feature is in use, with potentially malicious script content stored in image captions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.5.5.2
Interim mitigation

Update Beaver Builder to a version newer than 2.5.5.2. Until patched, restrict editor access to only highly trusted users and consider deploying a WAF to help detect XSS exploitation attempts.

Recommended fix Moderate confidence

Beaver Builder 2.5.5.3 or latest available version

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find 'Beaver Builder' in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/beaver-builder-lite-version/ or the premium Beaver Builder website
  6. 6. After updating, verify the plugin version is 2.5.5.3 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Beaver Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2517 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-2517 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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