dbcve.org
Happy Addons For ElementorWordPress extension · Leevio

CVE-2024-47357

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-06
Fix available
A fix is available. Upgrade to after 3.12.0 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 HappyMonster Happy Addons for Elementor happy-elementor-addons allows Stored XSS.This issue affects Happy Addons for Elementor: from n/a through <= 3.12.0.

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

Stored Cross-site Scripting (XSS) vulnerability in Happy Addons for Elementor plugin (versions <= 3.12.0) allows authenticated attackers to inject malicious JavaScript through unsanitized user input that gets stored in the database and executed when other users view affected pages.

MitigationUpdate Happy Addons for Elementor to the latest version (above 3.12.0) which includes proper input sanitization. Until patched, restrict user permissions to prevent low-privilege users from creating/editing content with the affected widgets.

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

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. Check Happy Addons for Elementor version
    In WordPress admin, go to Plugins > Installed Plugins > Happy Addons for Elementor and read the version number from the plugin description. Alternatively, check the main plugin file header in wp-content/plugins/happy-addons-for-elementor/
    Affected if Version number is 3.12.0 or lower
  2. Identify widgets with user input storage
    Review which Happy Addons widgets accept user-generated text input and store it to the database (such as form widgets, text display widgets, or any widget that saves input to post meta). Check if these widgets lack proper input validation in their frontend output.
    Affected if The site uses widgets from Happy Addons that accept and store user input without sanitizing output when rendered
  3. Search database for stored XSS payloads
    Query the WordPress database (wp_postmeta table and related tables) for common XSS patterns such as <script tags, javascript: URLs, onload/onevent attributes, or encoded payloads. Use SQL: SELECT * FROM wp_postmeta WHERE meta_value LIKE '%<script%' OR meta_value LIKE '%javascript:%'
    Affected if Records contain suspicious JavaScript code in meta values that could execute when pages load
  4. Inspect recent content created by lower-privilege users
    Review recent posts, pages, or widget instances created by users with Contributor or Author roles. Examine the content for unexpected script tags or event handlers in fields using Happy Addons widgets.
    Affected if Content created by non-administrator users contains unsanitized script content that would execute in other users browsers

A user is affected if Happy Addons for Elementor version is 3.12.0 or lower AND the site allows authenticated users to create or edit content using the affected 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.

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

Update Happy Addons for Elementor to the latest version (above 3.12.0) which includes proper input sanitization. Until patched, restrict user permissions to prevent low-privilege users from creating/editing content with the affected widgets.

Fix this in Happy Addons For Elementor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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