ElementsreadyWordPress extension · Quomodosoft
CVE-2024-47353
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 · uneditedURL Redirection to Untrusted Site ('Open Redirect') vulnerability in quomodosoft ElementsReady Addons for Elementor element-ready-lite.This issue affects ElementsReady Addons for Elementor: from n/a through 6.4.2.
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 confidenceOpen redirect vulnerability in the ElementsReady Addons for Elementor plugin (element-ready-lite) allows attackers to craft malicious URLs that appear to originate from the affected site but redirect users to untrusted external sites. This is a common vector for phishing attacks and can be exploited to trick users into believing they are visiting a legitimate page.
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
< 5.8.1CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify ElementsReady plugin installationLocate the element-ready-lite plugin directory in your WordPress installation, typically under wp-content/plugins/element-ready-lite/, or check for 'ElementsReady' or 'Quomodosoft' in your WordPress plugin admin panel.Affected if The plugin is installed and active on the site.
-
Identify installed plugin versionOpen the main plugin file (usually element-ready-lite.php) and locate the version constant (such as 'Version:' in the file header or a defined VERSION constant), or view the version listed in the WordPress Plugins admin page.Affected if The installed version is less than 5.8.1.
-
Confirm the plugin handles redirectsReview the plugin source code for functions that process redirect parameters (such as 'redirect', 'url', or 'target' query parameters) and determine if external URLs can be passed as values.Affected if The plugin contains redirect-handling functionality that accepts user-controlled URL parameters.
-
Check access to redirect functionalityTest whether the redirect endpoint is accessible without authentication by attempting a request with a redirect parameter pointing to an external domain (e.g., ?redirect=http://example.com), observing if the site issues a redirect response.Affected if The redirect functionality is accessible to unauthenticated users.
A site is affected if the ElementsReady (element-ready-lite) plugin is installed with a version lower than 5.8.1 and the redirect functionality is accessible to trigger open redirects.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data5.8.1
Update ElementsReady Addons for Elementor to a version newer than 6.4.2. If no patched version is available, consider removing or disabling the plugin until a fix is released.
Fix this in Elementsready
Scoped from the published advisory
- Consultation1.0 h
- Implementation0.5 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47353 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47353 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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