dbcve.org
Addons For ElementorWordPress extension · Livemeshelementor

CVE-2024-2655

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-10
Fix available
A fix is available. Upgrade to 8.3.6 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 Post widgets in all versions up to, and including, 8.3.5 due to insufficient input sanitization and output escaping on author display names. 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 plugin for WordPress is vulnerable to stored Cross-Site Scripting (XSS) in its Post widgets. The vulnerability stems from insufficient input sanitization and output escaping on author display names, allowing authenticated attackers with contributor-level access or higher to inject arbitrary JavaScript that executes whenever users access affected pages.

MitigationUpdate the Livemesh Elementor Addons plugin to version 8.3.6 or later, which includes proper sanitization and output escaping for author display names.

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

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 Livemesh Elementor Addons plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Livemesh Elementor Addons' or 'Livemesh Addons for Elementor'. Confirm it appears in the list.
    Affected if The plugin is installed and active
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins. Click on the plugin name to view details, or check the plugin header in /wp-content/plugins/ Addons-for-elementor/livemesh-addons-for-elementor.php for the 'Version' field.
    Affected if The version is less than 8.3.6 (e.g., 8.3.5, 8.3.0, etc.)
  3. Identify if Post widgets are in use
    Edit any page or post with Elementor. In the Elementor panel widget search, type 'Post' to list Post-related widgets (e.g., Post Grid, Post Block, Post Carousel, Posts Gallery). Check your published pages for instances of these widgets.
    Affected if Any Post widgets from this plugin are present on the site
  4. Check for contributor-level or higher user accounts
    In WordPress admin, go to Users > All Users. Review the list for any users with the role of Contributor, Author, Editor, or Administrator. Note that Contributor-level users can create posts but cannot publish without approval.
    Affected if There are users with Contributor, Author, Editor, or Administrator roles who could potentially modify author display names in Post widgets

A site is likely affected if the Livemesh Elementor Addons plugin version is below 8.3.6 and Post widgets from this plugin are in use on the site.

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 8.3.6 or later
Fixed in 8.3.6
Interim mitigation

Update the Livemesh Elementor Addons plugin to version 8.3.6 or later, which includes proper sanitization and output escaping for author display names.

Recommended fix High confidence

Addons For Elementor version 8.3.6

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > All Plugins in the WordPress admin dashboard
  3. Find 'Addons For Elementor' (also known as 'Livemesh Addons for Elementor')
  4. Click 'Update Now' to update the plugin to version 8.3.6 or later
  5. Verify the plugin was updated successfully by checking the installed version
  6. Clear any caching plugins if enabled
  7. Test that author display names are properly sanitized and the XSS vulnerability is resolved

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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