dbcve.org
Happy Addons For ElementorWordPress extension · Leevio

CVE-2024-29108

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to after 3.10.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 Leevio Happy Addons for Elementor allows Stored XSS.This issue affects Happy Addons for Elementor: from n/a through 3.10.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

A stored Cross-Site Scripting (XSS) vulnerability exists in Happy Addons for Elementor plugin versions up to 3.10.1. The plugin fails to properly neutralize user-supplied input during web page generation, allowing malicious JavaScript to be injected and persisted in the database. When other users view affected pages rendered by the Elementor page builder, the stored malicious script executes in their browsers.

MitigationUpdate Happy Addons for Elementor to the latest version that includes proper input sanitization and output encoding. Until a patch is available, restrict editor access to trusted users only and implement Content Security Policy headers.

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
Happy Addons For ElementorWordPress extension
Affected:<= 3.10.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 Happy Addons for Elementor is installed
    Navigate to WordPress admin > Plugins and locate 'Happy Addons for Elementor' in the installed plugins list. Note the installed version displayed next to the plugin name.
    Affected if The plugin is installed and the version listed is 3.10.1 or lower (any version up to and including 3.10.1).
  2. Confirm the plugin version number
    Click on the plugin in the WordPress plugins list to view its details, or check the version in the plugin's main PHP file (typically happy-addons-for-elementor.php) via file manager or FTP.
    Affected if The version number displayed is 3.10.1 or any version below it.
  3. Identify if Elementor page builder is active
    Check if Elementor page builder plugin is installed and active in the WordPress site. Navigate to Pages or Posts and verify existing content was created using the Elementor editor (indicated by 'Edit with Elementor' button).
    Affected if Elementor is active and being used to create or edit content on the site.
  4. Inspect pages using Happy Addons widgets
    Review pages or posts created with Elementor that include Happy Addons widgets. Examine text fields, heading fields, or any user-editable content areas within those widgets for unexpected script tags, javascript: URIs, or HTML event handlers (onload, onerror, onclick, etc.).
    Affected if Any page created with Elementor that uses Happy Addons widgets contains suspicious script injections or event handler attributes in its content fields.
  5. Examine database for persisted XSS payloads
    Query the wp_posts table (or custom prefix) in the database for any script tags or javascript: patterns within post_content, especially in posts where post_type is 'elementor_library' or 'page'/'post' and content was edited with Elementor.
    Affected if Database records show raw script tags, javascript: prefixes, or HTML event handlers stored in post content fields.

You are affected if Happy Addons for Elementor version 3.10.1 or lower is installed, Elementor is being used to create content, and any pages contain persisted malicious scripts in Happy Addons widget fields.

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.

From vendor data
Upgrade available Upgrade to a release after 3.10.1
Interim mitigation

Update Happy Addons for Elementor to the latest version that includes proper input sanitization and output encoding. Until a patch is available, restrict editor access to trusted users only and implement Content Security Policy headers.

Fix this in Happy Addons For Elementor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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