CVE-2024-5344
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 · uneditedThe The Plus Addons for Elementor Page Builder plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘forgoturl’ attribute within the plugin's WP Login & Register widget in all versions up to, and including, 5.5.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
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 confidenceThe Plus Addons for Elementor plugin's WP Login & Register widget fails to properly sanitize the 'forgoturl' parameter and escape output, allowing unauthenticated attackers to inject malicious JavaScript via crafted URLs. When a victim clicks a malicious link, the injected script executes in their browser, potentially stealing session cookies or performing actions as the victim.
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< 5.6.0CVSS 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.
-
Confirm plugin installation and versionLocate the plugin directory (typically /wp-content/plugins/the-plus-addons-for-elementor/) and read the main plugin file header or readme.txt to find the installed version number.Affected if The installed version is below 5.6.0 (any version prior to 5.6.0 is affected).
-
Identify use of WP Login & Register widgetSearch WordPress database or Elementor saved templates for the 'wp_login_register' widget type. Check pages, posts, and Elementor template library where this widget may have been added.Affected if The WP Login & Register widget from this plugin is actively used on any page or template on the site.
-
Inspect forgoturl configurationExamine Elementor page/post meta or template data where the WP Login & Register widget is placed. Look for the 'forgoturl' or 'forgot_password_url' attribute in the widget settings or stored data.Affected if The 'forgoturl' parameter is populated with any value, as the vulnerability exists regardless of what value is set (the flaw is in how the parameter handles input).
-
Test for reflected XSS via forgoturl parameterIf the widget is in use, visit a page with the widget and append '?forgoturl=javascript:alert(1)' to the URL. Observe whether the script executes or if the value appears reflected in the page source without proper escaping.Affected if The malicious payload is reflected in the page output or executes JavaScript, confirming the XSS vulnerability is present and exploitable.
The site is affected if The Plus Addons for Elementor is installed with a version below 5.6.0 AND the WP Login & Register widget is actively used, regardless of the forgoturl setting.
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.
dbcve · scoped5.6.0
Update The Plus Addons for Elementor to version 5.5.7 or later, which implements proper input sanitization and output escaping for the 'forgoturl' attribute. Until updated, users should not click untrusted links pointing to sites using this widget.
The Plus Addons For Elementor version 5.6.0 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'The Plus Addons for Elementor' in the plugin list
- Click 'Update now' if an update is available, or manually update to version 5.6.0 or later
- Verify the update completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5344 — 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-5344 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