Addons For ElementorWordPress extension · Livemeshelementor

CVE-2024-27986

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-14
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Livemesh Elementor Addons by Livemesh allows Stored XSS.This issue affects Elementor Addons by Livemesh: from n/a through 8.3.5.

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

A stored cross-site scripting (XSS) vulnerability in Livemesh Elementor Addons allows authenticated attackers to inject malicious JavaScript through unsanitized user input that gets stored and rendered in web pages without proper output encoding.

MitigationUpdate Livemesh Elementor Addons to the latest version beyond 8.3.5. If no patched version is available, consider removing the plugin or implementing a WAF rule to filter XSS payloads until a fix is released.

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 Livemesh Elementor Addons is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Livemesh Elementor Addons' or check the plugin file header in wp-content/plugins/elementor-addons-livemesh/includes/plugin.php
    Affected if The plugin is present in the installation
  2. Check installed plugin version
    In WordPress admin Plugins page, find 'Livemesh Elementor Addons' and read the version number displayed below the plugin name, or inspect the 'Version' header in the main plugin PHP file
    Affected if Version number is less than 8.3.6
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the 'Livemesh Elementor Addons' plugin shows as 'Active'
    Affected if Plugin is active and version is below 8.3.6
  4. Check for authenticated user accounts
    Review WordPress user list in Users > All Users to identify accounts with contributor, author, editor, or administrator roles who could access plugin features
    Affected if Authenticated users with access to plugin settings exist and plugin version is below 8.3.6

If the Livemesh Elementor Addons plugin is installed, active, and version is below 8.3.6, the environment is vulnerable to stored XSS via authenticated user input.

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 Livemesh Elementor Addons to the latest version beyond 8.3.5. If no patched version is available, consider removing the plugin or implementing a WAF rule to filter XSS payloads until a fix is released.

Recommended fix High confidence

8.3.6

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Addons For Elementor' (Livemesh Elementor Addons) in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 8.3.6
  5. After updating, verify the plugin version shows 8.3.6

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27986 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-27986 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