dbcve.org
Bold Page BuilderWordPress extension · Bold Themes

CVE-2024-30179

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

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

A stored cross-site scripting (XSS) vulnerability in BoldThemes Bold Page Builder allows authenticated attackers to inject malicious JavaScript through unsanitized input fields. This injected script is then rendered when users view affected pages, potentially leading to session hijacking or credential theft.

MitigationUpdate Bold Page Builder to the latest patched version that implements proper input sanitization and output encoding; until then, restrict or disable the plugin's editing capabilities for untrusted users.

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.7.7

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 is installed
    Check your WordPress plugins directory or admin panel for 'Bold Page Builder' or 'BoldThemes Bold Page Builder' plugin
    Affected if The plugin is installed and active in WordPress
  2. Check installed version number
    Navigate to WordPress admin > Plugins > Bold Page Builder and view the version number displayed, or check the plugin header in /wp-content/plugins/bold-page-builder/ directory
    Affected if Version is lower than 4.7.7 (e.g., 4.7.6, 4.6.x, etc.)
  3. Identify users with page builder access
    Review WordPress user roles and permissions that grant access to the page builder editor; check if low-privilege or untrusted users have 'edit pages' or 'edit posts' capabilities
    Affected if Untrusted or low-privilege users (subscribers, contributors, or limited editors) have access to use the page builder editor
  4. Inspect pages for suspicious injected scripts
    View page source or use browser developer tools to examine HTML output of pages created with the builder; look for unexpected <script> tags, event handlers (onclick, onerror, etc.), or javascript: URIs in input field values
    Affected if Unexpected JavaScript code is present in page content that was not intentionally added by administrators

You are affected if Bold Page Builder version is below 4.7.7 AND untrusted users have access to the builder, or if you observe unauthorized script injections in your published pages.

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.7.7 or later
Fixed in 4.7.7
Interim mitigation

Update Bold Page Builder to the latest patched version that implements proper input sanitization and output encoding; until then, restrict or disable the plugin's editing capabilities for untrusted users.

Recommended fix Moderate confidence

4.7.7

  1. 1. Navigate to the WordPress admin dashboard where Bold Page Builder is installed
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate Bold Page Builder in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 4.7.7
  5. 5. Alternatively, download version 4.7.7 from the official WordPress repository or BoldThemes and upload/install it manually
  6. 6. After updating, clear any caching plugins or server-side caches to ensure the patched version is served

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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