CVE-2024-0438
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 · uneditedThe Happy Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the wrapper link 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 confidenceThe Happy Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) in the Age Gate feature's wrapper link parameter. In versions up to and including 3.10.1, the plugin fails to properly sanitize input and escape output, allowing authenticated contributors or higher to inject malicious JavaScript that executes when users access affected pages.
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< 3.10.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Happy Addons for Elementor is installedLog into WordPress admin, go to Plugins list, or inspect the plugin directory /wp-content/plugins/happy-addons-for-elementor/ for the main plugin fileAffected if The plugin is not present in the installation
-
Check the installed version numberIn WordPress admin, view the plugin details on the Plugins page, or read the version header from the main plugin PHP file (typically happy-addons-for-elementor.php)Affected if The installed version is less than 3.10.2 (versions 3.10.1 and below are vulnerable)
-
Identify if Age Gate widget is in useReview pages and posts edited with Elementor that contain the Age Gate widget. Check Elementor saved templates or conduct a database search for posts containing the Age Gate widget shortcode or elementAffected if The Age Gate widget is present on any published page or post
-
Inspect the wrapper link parameterEdit pages with the Age Gate widget in Elementor, open the Age Gate settings panel, and examine the Wrapper Link field for any URL valueAffected if A wrapper link is configured and contains unsanitized JavaScript or HTML (e.g., javascript:alert(1))
You are affected if Happy Addons for Elementor version 3.10.1 or below is installed AND the Age Gate widget with a wrapper link is in use on your site.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.10.2
Update Happy Addons for Elementor to a version beyond 3.10.1 which includes proper input sanitization and output escaping for the wrapper link parameter. Until patched, limit contributor-level access or disable the Age Gate feature.
Happy Addons For Elementor 3.10.2
- Backup your WordPress site before making any changes
- Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- Find 'Happy Addons for Elementor' in the plugin list
- Click 'Update now' if an update is available, or manually upload version 3.10.2 from the WordPress plugin repository
- Verify the plugin version shows 3.10.2 after updating
- Clear any caching plugins or server-side caches
- Test that the Age Gate functionality works correctly with the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0438 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0438 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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