dbcve.org
Addons For ElementorWordPress extension · Livemeshelementor

CVE-2024-47303

MEDIUM · 5.4 CVSS v3.1 Published 2024-09-25
Fix available
A fix is available. Upgrade to 8.5.1 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 Livemesh Addons for Elementor addons-for-elementor allows Cross-Site Scripting (XSS).This issue affects Livemesh Addons for Elementor: from n/a through <= 8.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 · moderate confidence

Stored XSS vulnerability in Livemesh Addons for Elementor plugin allows authenticated attackers to inject malicious JavaScript through unsanitized input fields. The injected scripts execute when other users view pages containing the compromised content, potentially leading to session hijacking or credential theft.

MitigationUpdate Livemesh Addons for Elementor to the latest patched version. If immediate update is not possible, implement output encoding at the theme/template level or deploy a WAF rule to filter malicious script patterns.

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

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 Addons for Elementor is installed
    Navigate to WordPress admin > Plugins or use 'wp plugin list' via WP-CLI to list installed plugins. Look for 'Livemesh Addons for Elementor' or 'livemesh-elementor-addons' in the plugin list.
    Affected if The plugin is not found in the installed plugins list.
  2. Locate the installed version number
    In WordPress admin, go to Plugins > Installed Plugins > Livemesh Addons for Elementor and read the version number displayed below the plugin name. Alternatively, check the main plugin file (livemesh-elementor-addons.php) in wp-content/plugins/ and look for the 'Version' header comment.
    Affected if Unable to determine the version number from the plugin metadata.
  3. Compare version against the affected range
    Compare your installed version to the threshold 8.5.1. The vulnerability affects all versions below 8.5.1 (e.g., 8.4.0, 8.3.1, 8.0, 7.0, etc.).
    Affected if The installed version is a release prior to 8.5.1 (e.g., 8.4.x, 8.3.x, or lower).
  4. Identify if unauthenticated or low-privilege input fields exist
    Review Elementor page builder content that uses Livemesh widgets (such as posts grid, portfolio, carousel, or team members widgets). Check for any user-submitted content displayed on the frontend that could contain unsanitized script tags.
    Affected if Livemesh widgets are in use and accept or display user-generated content without apparent output encoding.

The environment is affected if Livemesh Addons for Elementor is installed with a version number lower than 8.5.1.

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.5.1 or later
Fixed in 8.5.1
Interim mitigation

Update Livemesh Addons for Elementor to the latest patched version. If immediate update is not possible, implement output encoding at the theme/template level or deploy a WAF rule to filter malicious script patterns.

Recommended fix High confidence

8.5.1

  1. Backup your WordPress site and database before making any changes
  2. Navigate to Plugins > All Plugins in the WordPress admin dashboard
  3. Find 'Livemesh Addons for Elementor' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 8.5.1
  5. After updating, verify the plugin version shows 8.5.1 or higher
  6. Test the website frontend and Elementor editor to ensure functionality

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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