dbcve.org
Bold Page BuilderWordPress extension · Bold Themes

CVE-2023-49823

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-15
Fix available
A fix is available. Upgrade to after 4.6.1 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in BoldThemes Bold Page Builder allows Stored XSS.This issue affects Bold Page Builder: from n/a through 4.6.1.

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

A stored Cross-Site Scripting (XSS) vulnerability exists in BoldThemes Bold Page Builder versions up to 4.6.1. The plugin fails to properly sanitize user input during web page generation, allowing attackers to inject malicious JavaScript that executes when other users view the compromised content.

MitigationImplement proper output encoding and input sanitization across all user input fields in the page builder, particularly in areas where content is rendered publicly. Update to the latest patched version if available.

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
Bold Page BuilderWordPress extension
Affected:<= 4.6.1

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 Bold Page Builder plugin is installed
    Locate the plugin directory at wp-content/plugins/ and confirm the presence of the 'bt_plugin' or 'bold-page-builder' folder. Alternatively, check the WordPress admin under Plugins > Installed Plugins for 'Bold Page Builder' or 'BoldThemes Bold Page Builder'.
    Affected if The plugin is installed and active in WordPress.
  2. Check the installed plugin version
    Open the main plugin PHP file (typically bold-page-builder/bold-page-builder.php) and locate the version header in the plugin comments, or check the readme.txt file for the 'Stable tag' version number.
    Affected if The version is 4.6.1 or lower.
  3. Confirm the plugin is active
    In WordPress admin, navigate to Plugins > Installed Plugins and verify that Bold Page Builder shows as 'Active'. Alternatively, query the wp_options table for option_name = 'active_plugins' and check if the plugin slug is present in the serialized array.
    Affected if The plugin is active on the WordPress site.
  4. Inspect page builder content for unsanitized input
    Review pages/posts created using the Bold Page Builder. Access the edit screen for posts using the builder, or query the wp_postmeta table for meta_key containing 'bold_page_builder' or 'bt_builder_data'. Examine the stored content for unescaped HTML attributes, script tags, or event handlers in custom code elements, buttons, or text modules.
    Affected if User-supplied content in page builder fields contains raw HTML, script tags, or JavaScript event handlers (onclick, onerror, etc.) that would execute when viewed.

You are affected if the Bold Page Builder plugin is active and the installed version is 4.6.1 or lower, or if you find unsanitized script content stored in page builder data.

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 4.6.1
Interim mitigation

Implement proper output encoding and input sanitization across all user input fields in the page builder, particularly in areas where content is rendered publicly. Update to the latest patched version if available.

Recommended fix Moderate confidence

Bold Page Builder version > 4.6.1

  1. 1. Identify the currently installed Bold Page Builder version in your WordPress installation
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Check if a newer version of Bold Page Builder is available for download
  4. 4. If a newer version (greater than 4.6.1) is available, update the plugin to the latest version
  5. 5. Verify the update completed successfully
  6. 6. Test the functionality of the page builder to ensure it works correctly after the update

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

Fix this in Bold Page Builder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49823 — 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-2023-49823 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