dbcve.org
Bold Page BuilderWordPress extension · Bold Themes

CVE-2024-30442

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-29
Fix available
A fix is available. Upgrade to 4.8.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.8.0.

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 up to version 4.8.0. The plugin fails to properly neutralize user-supplied input during web page generation, allowing malicious scripts to be stored and executed when administrators or other users view the affected content.

MitigationUpdate Bold Page Builder to the latest version when available, which should include proper input sanitization. Until patched, review and sanitize any user-generated content within the builder, and implement Content Security Policy (CSP) headers to mitigate XSS execution.

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.8.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. Check Bold Page Builder plugin version
    In WordPress admin, go to Plugins > Installed Plugins, locate 'Bold Page Builder' by Bold Themes, and note the version number displayed. Alternatively, check the plugin's main PHP file header or version.php for the version constant.
    Affected if Version is 4.8.0 or lower (any version below 4.8.1 is affected)
  2. Confirm the plugin is active and in use
    Verify the Bold Page Builder plugin is activated in WordPress. Check if pages or posts are using the builder by viewing page editing screens - if Bold Page Builder blocks or interface elements are present, the plugin is in use.
    Affected if Plugin is active and being used to create or edit site content
  3. Identify user-generated content created with the builder
    Review posts, pages, or custom post types that were built using the Bold Page Builder. Look for any fields that accept user input such as text elements, custom HTML, or content blocks where site visitors or contributors can submit content.
    Affected if Any content created with the builder accepts and stores user input that gets rendered on the frontend

You are affected if Bold Page Builder version is below 4.8.1 AND the builder is actively used to render content that includes user-supplied input without additional sanitization.

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

Update Bold Page Builder to the latest version when available, which should include proper input sanitization. Until patched, review and sanitize any user-generated content within the builder, and implement Content Security Policy (CSP) headers to mitigate XSS execution.

Recommended fix High confidence

4.8.1

  1. Update the Bold Page Builder plugin to version 4.8.1 or later via WordPress admin dashboard (Plugins > Updates or directly from the plugin page)
  2. Verify the update was successful by checking the installed version in WordPress admin under Plugins > Installed Plugins
  3. Clear any site caching mechanisms (page cache, CDN cache) to ensure the patched version is served
  4. Test the previously vulnerable functionality to confirm the stored 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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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