dbcve.org
Happy Addons For ElementorWordPress extension · Leevio

CVE-2024-0838

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to after 3.10.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
The Happy Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the side image URL parameter in the Age Gate in all versions up to, and including, 3.10.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access or higher, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE-2024-29108 is likely a duplicate of this issue.

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

The Happy Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) in the Age Gate feature's side image URL parameter. Due to insufficient input sanitization and output escaping, authenticated attackers with contributor-level access or higher can inject arbitrary JavaScript that executes whenever users access injected pages. The vulnerability affects all versions up to and including 3.10.1.

MitigationUpdate Happy Addons for Elementor to version 3.10.2 or later to resolve the insufficient sanitization and escaping. Alternatively, remove the plugin if no update is available.

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.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. Verify Happy Addons for Elementor is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Happy Addons for Elementor' by Leevio. Alternatively, check the /wp-content/plugins/ directory for the happy-addons-for-elementor folder.
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click on the Happy Addons for Elementor plugin to view its version, or inspect the main plugin file (happy-addons-for-elementor.php) and look for the 'Version:' header comment.
    Affected if Version is 3.10.1 or lower, or any version up to and including 3.10.2
  3. Determine if the Age Gate widget is in use
    Go to Pages or Posts in WordPress admin and edit any pages. In the Elementor editor, search for 'Age Gate' in the widget panel. Alternatively, search the wp_postmeta database table for meta_value containing 'age-gate' or check page templates for the Age Gate widget element.
    Affected if The Age Gate widget from Happy Addons has been added to any page or post on the site
  4. Inspect the Age Gate side image URL setting
    Edit a page with the Age Gate widget in Elementor. Click on the Age Gate widget settings. Look for a 'Side Image' or 'Image' field in the widget panel. Check if a URL is populated in this field.
    Affected if A custom URL is set in the side image field - this is the vulnerable parameter where XSS can be injected

The environment is affected if Happy Addons for Elementor version 3.10.2 or below is installed AND the Age Gate widget with a side image URL configured is in use on the site.

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 a release after 3.10.2
Interim mitigation

Update Happy Addons for Elementor to version 3.10.2 or later to resolve the insufficient sanitization and escaping. Alternatively, remove the plugin if no update is available.

Recommended fix High confidence

Happy Addons for Elementor version 3.10.2 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find 'Happy Addons for Elementor' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the Age Gate widget functions correctly

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

Fix this in Happy Addons For Elementor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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