dbcve.org
ElementsreadyWordPress extension · Quomodosoft

CVE-2024-34374

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-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 allows Stored XSS.This issue affects ElementsReady Addons for Elementor: from n/a through 5.8.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

Stored Cross-site Scripting (XSS) vulnerability in QuomodoSoft ElementsReady Addons for Elementor allows attackers to inject malicious JavaScript through unsanitized input fields. This malicious script executes in the browsers of users who view the affected pages, enabling session hijacking, credential theft, or defacement.

MitigationUpdate ElementsReady Addons for Elementor to the latest version once available, or apply vendor-supplied patch. Sanitize all user inputs and implement output encoding on existing pages.

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 dashboard, navigate to Plugins > Installed Plugins, and search for 'ElementsReady' or 'Quomodosoft Elementsready'
    Affected if The plugin appears in the installed plugins list and is activated
  2. Determine installed version number
    In the same plugins list, locate the ElementsReady plugin and note the version number displayed beneath the plugin name
    Affected if Version number is visible and is below 5.8.1
  3. Compare version to affected range
    Take the installed version (e.g., 5.7.0, 5.6.2) and compare it numerically to 5.8.1 - any version less than 5.8.1 falls within the affected range
    Affected if Installed version is less than 5.8.1 (for example: 5.8.0, 5.7.5, 5.6.0, etc.)
  4. Confirm plugin has user input functionality
    Review the site frontend or Elementor editor to check if any ElementsReady widgets or modules that accept user input (forms, contact fields, submission widgets) are in use on published pages
    Affected if The vulnerable input-handling widgets are active on any public-facing page

You are affected if the ElementsReady Addons for Elementor plugin is installed, activated, and the installed version is less than 5.8.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 5.8.1 or later
Fixed in 5.8.1
Interim mitigation

Update ElementsReady Addons for Elementor to the latest version once available, or apply vendor-supplied patch. Sanitize all user inputs and implement output encoding on existing pages.

Recommended fix High confidence

ElementsReady Addons for Elementor version 5.8.1 or later

  1. 1. Create a full backup of your WordPress site including database and files
  2. 2. Navigate to WordPress admin dashboard > Plugins
  3. 3. Find the ElementsReady Addons for Elementor plugin
  4. 4. Click Update to install version 5.8.1 or later
  5. 5. After update completes, verify the plugin version shows 5.8.1 or higher
  6. 6. Clear any site caching layers (CDN, caching plugins) to ensure changes take effect
  7. 7. Test affected functionality to confirm normal operation

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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