dbcve.org
ElementsreadyWordPress extension · Quomodosoft

CVE-2024-51787

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-09
Fix available
A fix is available. Upgrade to 6.4.4 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 quomodosoft ElementsReady Addons for Elementor element-ready-lite allows Stored XSS.This issue affects ElementsReady Addons for Elementor: from n/a through <= 6.4.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 · moderate confidence

Stored XSS vulnerability in the element-ready-lite plugin for WordPress/Elementor allows attackers to inject malicious scripts into web pages that are then executed when other users view the compromised content.

MitigationUpdate element-ready-lite to the latest patched version once available, or implement input sanitization/validation on plugin output functions to prevent script execution.

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
ElementsreadyWordPress extension
Affected:< 6.4.4

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 element-ready-lite plugin is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for the element-ready-lite folder
    Affected if The plugin folder exists in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, find the element-ready-lite plugin in the plugins list and note the version number displayed below the plugin name
    Affected if The installed version is lower than 6.4.4 (for example, 6.4.3, 6.4.0, or any version below 6.4.4)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify that element-ready-lite shows as Active (not deactivated or inactive)
    Affected if The plugin is currently active and the version is below 6.4.4
  4. Inspect pages built with Elementor for suspicious script tags
    Use browser developer tools to view the source code of pages that use the plugin's widgets, or query the wp_posts table for entries containing script tags in post_content where post_type is elementor_cpt or similar
    Affected if Malicious script tags are present in page content that originated from element-ready-lite widget output
  5. Review Elementor custom widget configurations
    Export Elementor data via Tools > Import/Export and inspect JSON for any unexpected JavaScript or event handlers in element-ready-lite widget settings
    Affected if Encoded or plaintext script tags, onerror attributes, or javascript: URIs are found in widget settings

The environment is affected if the element-ready-lite plugin is installed, active, and running at a version below 6.4.4, with malicious scripts potentially present in Elementor pages or widget data.

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

Update element-ready-lite to the latest patched version once available, or implement input sanitization/validation on plugin output functions to prevent script execution.

Recommended fix High confidence

ElementsReady Addons for Elementor (element-ready-lite) version 6.4.4

  1. Backup your WordPress site before making any changes
  2. Update the element-ready-lite plugin to version 6.4.4 or later via the WordPress plugin dashboard, or upload the updated plugin package
  3. Verify the update was successful by checking the plugin version in the WordPress admin
  4. Clear any caching mechanisms if used, as XSS payloads may be cached

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

Fix this in Elementsready Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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