dbcve.org
Bold Page BuilderWordPress extension · Bold Themes

CVE-2024-47298

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-06
Fix available
A fix is available. Upgrade to 5.1.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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in boldthemes Bold Page Builder bold-page-builder allows Stored XSS.This issue affects Bold Page Builder: from n/a through <= 5.1.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 · moderate confidence

Stored Cross-site Scripting (XSS) vulnerability in the Bold Page Builder WordPress plugin allows unauthenticated attackers to inject malicious JavaScript through unsanitized input fields. The malicious script is stored on the server and executes in the context of victim users' browsers when they view pages containing the injected content.

MitigationUpdate Bold Page Builder to the latest patched version. As a temporary control, deploy a WAF rule to filter XSS payloads in plugin input fields until the update can be applied.

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:< 5.1.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. Confirm Bold Page Builder is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Bold Page Builder' by Bold Themes, or inspect the plugin directory /wp-content/plugins/bt-core or similar Bold Page Builder folders
    Affected if The plugin is present on the WordPress site
  2. Identify the installed version
    In Plugins list, find Bold Page Builder and note the version number displayed under the plugin name, or check the main plugin PHP file for the 'Version' header in the plugin comments
    Affected if The version is lower than 5.1.2
  3. Verify the plugin is active
    In WordPress admin > Plugins, check that Bold Page Builder shows as 'Active' rather than 'Inactive'
    Affected if The plugin is active and being used on live pages
  4. Inspect page builder input fields for unsanitized content
    Use the Bold Page Builder to create or edit a page, locate text input fields (such as heading fields, text content fields, or custom text modules), and examine the HTML source of rendered pages using browser developer tools to see if input is properly escaped
    Affected if User-supplied input appears raw in HTML without encoding (e.g., <script> tags visible in page source)

If Bold Page Builder version is below 5.1.2 and the plugin is active, the site is vulnerable to stored XSS attacks via unsanitized input fields in the page builder.

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 5.1.2 or later
Fixed in 5.1.2
Interim mitigation

Update Bold Page Builder to the latest patched version. As a temporary control, deploy a WAF rule to filter XSS payloads in plugin input fields until the update can be applied.

Recommended fix High confidence

Bold Page Builder version 5.1.2

  1. 1. Backup your WordPress site and database before performing any updates.
  2. 2. Update Bold Page Builder plugin to version 5.1.2 or later.
  3. 3. Verify the update was successful by checking the plugin version in WordPress admin under Plugins > Installed Plugins.
  4. 4. Clear any server-side and CDN caches to ensure the updated files are served.
  5. 5. Test the affected functionality to confirm the XSS vulnerability is remediated.

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

Fix this in Bold Page Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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