dbcve.org
Addons For ElementorWordPress extension · Livemeshelementor

CVE-2024-3639

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-04
Fix available
A fix is available. Upgrade to after 8.3.7 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 Elementor Addons by Livemesh plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Posts Grid widget in all versions up to, and including, 8.3.7 due to insufficient input sanitization and output escaping on user supplied attributes like 'grid_skin'. 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

The Elementor Addons by Livemesh WordPress plugin versions up to 8.3.7 contain a stored XSS vulnerability in the Posts Grid widget. The 'grid_skin' attribute and similar user-supplied attributes are not properly sanitized before storage or escaped upon output, allowing authenticated attackers with contributor-level permissions to inject malicious JavaScript that executes whenever users access affected pages.

MitigationUpdate the plugin to version 8.3.8 or later. If immediate update is not possible, restrict contributor-level user permissions or disable the Posts Grid widget until the patch can be applied.

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
Addons For ElementorWordPress extension
Affected:<= 8.3.7

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 the installed plugin version
    Navigate to WordPress Admin > Plugins > Installed Plugins > Livemesh Elementor Addons and check the version number displayed
    Affected if The version shown is 8.3.7 or lower
  2. Confirm the Posts Grid widget is in use
    Search your pages and posts for instances of the Posts Grid widget added via Elementor - check page content or use a site search for 'posts-grid' or the widget name
    Affected if The Posts Grid widget is present on any published page or post
  3. Review contributor-level user accounts
    Go to WordPress Admin > Users and review the user list for any accounts with Contributor role
    Affected if There are one or more contributor-level users who could have authored malicious content
  4. Inspect recent posts authored by contributors
    Review posts/pages created by contributor users, particularly those using the Posts Grid widget, for suspicious script tags or event handlers in attribute fields
    Affected if Unexpected script tags, javascript: URLs, or on* event handlers are found in grid attribute fields

You are affected if the Livemesh Elementor Addons plugin version is 8.3.7 or lower AND the Posts Grid widget is in use on your site, as the unsanitized grid_skin attribute allows stored XSS injection by contributor-level users.

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 8.3.7
Interim mitigation

Update the plugin to version 8.3.8 or later. If immediate update is not possible, restrict contributor-level user permissions or disable the Posts Grid widget until the patch can be applied.

Recommended fix Moderate confidence

8.3.8 or later

  1. 1. Back up the WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the 'Addons For Elementor' (also known as 'Elementor Addons by Livemesh') plugin
  4. 4. Click 'Update Now' if an update is available, or manually download version 8.3.8 or higher from wordpress.org
  5. 5. After updating, verify the new version number in the plugins list
  6. 6. Test the Posts Grid widget functionality to ensure the update did not break existing features
  7. 7. Clear any caching plugins or server-side caches

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

Fix this in Addons For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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 locally
dbcve dependency scanner

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