dbcve.org
StaxWordPress extension · Staxwp

CVE-2024-37541

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-06
Fix available
A fix is available. Upgrade to after 1.4.4.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 StaxWP Elementor Addons, Widgets and Enhancements – Stax stax-addons-for-elementor allows DOM-Based XSS.This issue affects Elementor Addons, Widgets and Enhancements – Stax: from n/a through <= 1.5.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

DOM-based Cross-site Scripting (XSS) vulnerability in StaxWP Elementor Addons allows attackers to inject malicious JavaScript through unsanitized user input that gets dynamically inserted into the web page's DOM. This is a client-side vulnerability where the plugin fails to properly sanitize or encode input before rendering it in the browser.

MitigationUpgrade to a version beyond 1.5.0 when available; otherwise, implement proper output encoding/sanitization on all user input paths in the JavaScript code before DOM insertion.

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
StaxWordPress extension
Affected:<= 1.4.4.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 Staxwp Stax installation and version
    Check the plugin/theme version file - typically in the main plugin PHP file or style.css header for themes. Look for version strings like 'Version: 1.4.4.1' or similar.
    Affected if The installed version is 1.4.4.1 or any version lower than 1.4.4.1 (i.e., version <= 1.4.4.1)
  2. Identify if Elementor Addons are active
    Check if the StaxWP Elementor Addons plugin is active in WordPress admin under Plugins, or if the Staxwp Stax theme with Elementor integration is in use.
    Affected if The plugin/theme is active with a vulnerable version
  3. Inspect for user input widgets or custom elements
    Review pages built with Elementor that use StaxWP widgets. Look for widgets that accept user input or display dynamic content such as custom heading widgets, text widgets, or any widget that might render user-supplied values into the DOM.
    Affected if StaxWP widgets handling user-supplied input are in use on the site
  4. Check browser console for XSS indicators
    Use browser developer tools to inspect elements and console for any unexpected script execution or errors related to StaxWP components. Manually test input fields with a benign test string like '<script>console.log(1)</script>' to see if it gets executed.
    Affected if User input is being executed as JavaScript in the browser DOM without proper encoding

You are affected if Staxwp Stax version 1.4.4.1 or lower is installed AND the site uses StaxWP Elementor Addons that handle user input which gets dynamically rendered to the page.

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 a release after 1.4.4.1
Interim mitigation

Upgrade to a version beyond 1.5.0 when available; otherwise, implement proper output encoding/sanitization on all user input paths in the JavaScript code before DOM insertion.

Recommended fix Moderate confidence

Version 1.5.1 or later (latest stable release)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find 'Elementor Addons, Widgets and Enhancements – Stax' (stax-addons-for-elementor)
  4. 4. Check the current installed version number
  5. 5. If the installed version is 1.5.0 or below, navigate to Plugins > Add New > Upload Plugin or check for plugin updates
  6. 6. Update to the latest available version of the Stax plugin (version 1.5.1 or higher, as this CVE affects versions through 1.5.0)
  7. 7. Verify the update completed successfully and test the site frontend and Elementor editor to confirm functionality

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

Fix this in Stax Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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