dbcve.org
Wpb Elementor AddonsWordPress extension · Wpbean

CVE-2024-34791

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-03
Fix available
A fix is available. Upgrade to 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 (XSS or 'Cross-site Scripting') vulnerability in wpbean WPB Elementor Addons allows Stored XSS.This issue affects WPB Elementor Addons: from n/a through 1.0.9.

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 WPB Elementor Addons plugin allows authenticated attackers to inject malicious JavaScript payloads through plugin widgets that are not properly sanitized before being stored and rendered in web pages, leading to script execution when users view affected content.

MitigationUpdate WPB Elementor Addons to the latest patched version. If no update is available, implement output encoding and input validation on plugin widget outputs, or disable the affected plugin until a fix is released.

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
Wpb Elementor AddonsWordPress extension
Affected:< 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 WPB Elementor Addons is installed
    Navigate to WordPress admin > Plugins and locate 'WPB Elementor Addons' in the installed plugins list. Note whether it is active or inactive.
    Affected if The plugin is installed and active, exposing the vulnerable widget functionality.
  2. Identify the installed plugin version
    In the Plugins page, click on the plugin name to view its details, or check the plugin header in /wp-content/plugins/wpb-elementor-addons/ folder for the version number.
    Affected if The installed version is lower than 1.2, meaning the vulnerability is present.
  3. Verify Elementor Page Builder is active
    Check that the Elementor website builder plugin is also installed and active, as WPB Elementor Addons requires it to function.
    Affected if Both plugins are active, allowing the vulnerable widgets to render on the site.
  4. Inspect widget output for unsanitized content
    Review pages/posts created with Elementor that use WPB addons. Check the HTML source of rendered pages for any user-supplied data in widget parameters that appears unescaped (e.g., raw HTML tags, event handlers).
    Affected if Widget outputs contain raw HTML or JavaScript that was not sanitized, indicating the XSS vulnerability is exploitable.

A site is affected if WPB Elementor Addons version is below 1.2, the plugin is active, and Elementor is enabled, allowing stored XSS payloads to execute when viewing pages with the vulnerable widgets.

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

Update WPB Elementor Addons to the latest patched version. If no update is available, implement output encoding and input validation on plugin widget outputs, or disable the affected plugin until a fix is released.

Recommended fix High confidence

WPB Elementor Addons version 1.2 or later

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Find 'WPB Elementor Addons' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.2 or later
  5. 5. Alternatively, download the latest version from the WordPress plugin repository or the vendor's website
  6. 6. After updating, verify the plugin version shows 1.2 or higher under Plugins > Installed Plugins
  7. 7. 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 Wpb Elementor Addons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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