dbcve.org
Addons For ElementorWordPress extension · Livemeshelementor

CVE-2024-25598

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-15
Fix available
A fix is available. Upgrade to 8.3.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 allows Stored XSS.This issue affects Livemesh Addons for Elementor: from n/a through 8.3.

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

Stored XSS vulnerability in Livemesh Addons for Elementor plugin allows attackers to inject malicious JavaScript through unsanitized input fields. The injected script executes when other users view affected pages in the WordPress admin or frontend.

MitigationUpdate Livemesh Addons for Elementor to the latest version which includes proper input sanitization and output encoding. Until then, restrict administrative access and validate all user-supplied content.

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.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
    Access WordPress admin dashboard, navigate to Plugins section, locate 'Livemesh Addons for Elementor' or 'Livemeshelementor Addons For Elementor' in the installed plugins list
    Affected if The plugin is not found in the plugins list
  2. Check installed plugin version
    In WordPress admin Plugins page, click on the plugin name or view details to display the installed version number
    Affected if Installed version is lower than 8.3.1
  3. Confirm Elementor page builder is active
    Navigate to WordPress Plugins page and verify Elementor website builder plugin is installed and activated
    Affected if Elementor is not active - the Livemesh plugin requires Elementor to function and expose its vulnerable input fields
  4. Inspect Livemesh widget settings for injected scripts
    Edit any page/post using Elementor, select a Livemesh widget (such as heading, button, or any Livemesh-specific widget), inspect the text input fields in the widget panel for suspicious script tags or javascript: URIs
    Affected if Any Livemesh widget settings contain unsanitized script content that would execute when viewed
  5. Check frontend/admin pages for unexpected script execution
    View pages on the WordPress site frontend and navigate through admin pages that display Livemesh widget content, look for unexpected alert dialogs or script behavior
    Affected if JavaScript executes when loading pages containing Livemesh widgets with injected payload

User is affected if Livemesh Addons for Elementor version is below 8.3.1 AND Elementor is active AND the plugin widgets are in use on the site, as the vulnerability requires the plugin to be installed with its vulnerable input fields exposed through Elementor.

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.1 or later
Fixed in 8.3.1
Interim mitigation

Update Livemesh Addons for Elementor to the latest version which includes proper input sanitization and output encoding. Until then, restrict administrative access and validate all user-supplied content.

Recommended fix High confidence

8.3.1

  1. Backup your WordPress site before making any changes
  2. Review the plugin changelog for version 8.3.1 to check for any breaking changes or deprecations
  3. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  4. Find 'Livemesh Addons for Elementor' in the plugin list
  5. Click 'Update now' if an update is available, or manually upload version 8.3.1 of the plugin
  6. After updating, clear any caching plugins or server-side caches
  7. Test the plugin functionality to ensure all features work correctly after the update
  8. Verify the XSS vulnerability is remediated by testing the affected input fields
Caveat Review the official changelog at livemesh.co for any breaking changes between your current version and 8.3.1 before upgrading

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 / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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