dbcve.org
ElementsreadyWordPress extension · Quomodosoft

CVE-2024-47329

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-06
Fix available
A fix is available. Upgrade to 5.8.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 quomodosoft ElementsReady Addons for Elementor element-ready-lite allows Cross-Site Scripting (XSS).This issue affects ElementsReady Addons for Elementor: from n/a through <= 6.4.0.

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

Cross-site scripting (XSS) vulnerability in the element-ready-lite WordPress plugin for Elementor allows attackers to inject malicious scripts into web pages through unsanitized user input. This affects versions up to and including 6.4.0.

MitigationUpdate the ElementsReady Addons for Elementor plugin to the latest available version beyond 6.4.0, which should contain the XSS vulnerability fix.

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:< 5.8.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 ElementsReady plugin is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/elementsready directory exists on the server
    Affected if The ElementsReady or ElementsReady Addons for Elementor plugin is present in the WordPress installation
  2. Identify the installed version number
    In WordPress admin, find the plugin in the Plugins list and note the version number displayed beneath the plugin name, or read the version from the plugin's main PHP file header (usually elementsready.php)
    Affected if The installed version is 6.4.0 or lower, OR the version is below 5.8.1 (depending on which version numbering the installed plugin uses)
  3. Confirm the vulnerable code path exists
    Check if the plugin files contain the element-ready-lite components by looking for files related to user input handling or form rendering within the plugin directory, as XSS requires unsanitized input fields to be rendered on the frontend
    Affected if The plugin is installed with a vulnerable version and the frontend features that accept user input are active on the site

The environment is affected if the ElementsReady/element-ready-lite plugin is installed with version 6.4.0 or lower (or version below 5.8.1 per the product listing), as this version contains the unsanitized user input that allows cross-site scripting.

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

Update the ElementsReady Addons for Elementor plugin to the latest available version beyond 6.4.0, which should contain the XSS vulnerability fix.

Recommended fix High confidence

5.8.1 or latest stable release

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'ElementsReady Addons for Elementor' (or element-ready-lite) plugin
  4. Check the current version number to confirm it is below 5.8.1
  5. Click 'Update Now' if an update is available, or manually download version 5.8.1 or later from a trusted source (e.g., WordPress.org or the official vendor)
  6. If no update notification appears, navigate to Plugins > Add New > Upload Plugin and upload the latest version
  7. Activate the updated plugin
  8. Clear any site caches if caching plugins are in use

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

Fix this in Elementsready Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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