dbcve.org
Happy Addons For ElementorWordPress extension · Leevio

CVE-2024-6627

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-27
Fix available
A fix is available. Upgrade to after 3.11.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 plugin's PDF View widget in all versions up to, and including, 3.11.2 due to insufficient input sanitization and output escaping on user supplied attributes. 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

Happy Addons for Elementor plugin versions up to 3.11.2 contain a stored XSS vulnerability in the PDF View widget due to insufficient input sanitization and output escaping on user-supplied attributes. Authenticated attackers with contributor-level permissions can inject malicious JavaScript that executes whenever users access affected pages.

MitigationUpdate Happy Addons for Elementor to version 3.11.3 or later. If the plugin is unused, consider removing it entirely to reduce attack surface.

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.11.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. Confirm Happy Addons for Elementor is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins, or 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, go to Plugins > Installed Plugins and find Happy Addons for Elementor to view the version number, or check the main plugin PHP file for the Version header
    Affected if The version number is 3.11.2 or lower
  3. Identify pages using the PDF View widget
    Search WordPress content for elements containing the PDF View widget. This can be done by reviewing pages and posts edited with Elementor, or by querying the WordPress database for postmeta entries containing 'pdf_view' or widget references to the PDF View component
    Affected if Any pages or posts contain the PDF View widget from Happy Addons
  4. Inspect PDF View widget settings for suspicious content
    Edit pages containing the PDF View widget in Elementor and examine all text input fields in the widget panel. Look for unexpected script tags, javascript: URLs, or HTML attributes containing event handlers like onload, onerror, or onmouseover
    Affected if Any PDF View widget settings contain malicious script injections or unexpected HTML/JavaScript code

A user is affected if Happy Addons for Elementor version 3.11.2 or lower is installed AND the PDF View widget is being used on any page or post with injected malicious scripts in its settings.

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

Update Happy Addons for Elementor to version 3.11.3 or later. If the plugin is unused, consider removing it entirely to reduce attack surface.

Recommended fix Moderate confidence

Happy Addons for Elementor version 3.11.3 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate '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 wordpress.org and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the PDF View widget settings are intact and functioning 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
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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