dbcve.org
Happy Addons For ElementorWordPress extension · Leevio

CVE-2024-1377

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-07
Fix available
A fix is available. Upgrade to after 3.10.3 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 ‘author_meta_tag’ attribute of the Author Meta widget in all versions up to, and including, 3.10.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 XSS vulnerability in Happy Addons for Elementor plugin's Author Meta widget where the 'author_meta_tag' attribute lacks proper input sanitization and output escaping, allowing authenticated contributors+ to inject malicious JavaScript that executes when users view injected pages.

MitigationUpdate Happy Addons for Elementor to version 3.10.4 or later; if unable to update immediately, restrict contributor-level access or disable the Author Meta widget until patched.

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

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 Happy Addons for Elementor is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Happy Addons for Elementor', or check the version via FTP in /wp-content/plugins/happy-addons-for-elementor/
    Affected if Plugin is not installed - not affected. If installed, continue to version check.
  2. Check installed version number
    View the plugin version in the WordPress plugin list or read the main plugin file header (e.g., happy-addons-for-elementor.php) to find the 'Version' field
    Affected if Version is 3.10.3 or lower - vulnerable. Version 3.10.4 or higher - not affected. If version cannot be determined, assume affected.
  3. Identify if Author Meta widget is in use
    In Elementor editor, search for 'Author Meta' widget in the widget panel, or use a database query: SELECT * FROM wp_posts WHERE post_content LIKE '%author_meta_tag%' AND post_status='publish'
    Affected if Author Meta widget is actively used on published pages - at risk. Widget not in use - lower risk but still vulnerable if plugin is outdated.
  4. Review user roles with contributor access
    Go to Users > All Users in WordPress admin and check for accounts with 'Contributor' role or higher
    Affected if There are contributor or higher-level users, the exploitation vector exists - review their activity logs.

You are affected if Happy Addons for Elementor version 3.10.3 or lower is installed AND the Author Meta widget is in use on your site, regardless of whether contributor users exist since the vulnerability can be exploited by any authenticated contributor+ user.

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.3
Interim mitigation

Update Happy Addons for Elementor to version 3.10.4 or later; if unable to update immediately, restrict contributor-level access or disable the Author Meta widget until patched.

Fix this in Happy Addons For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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