dbcve.org
Xpro Addons For ElementorWordPress extension · Wpxpro

CVE-2024-43150

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to 1.4.4.3 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 (XSS or 'Cross-site Scripting') vulnerability in Xpro Xpro Elementor Addons allows Stored XSS.This issue affects Xpro Elementor Addons: from n/a through 1.4.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 confidence

This is a Stored Cross-Site Scripting (XSS) vulnerability in the Xpro Elementor Addons WordPress plugin. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized user input that is stored in the database and executed when other users view the affected content within the Elementor page builder.

MitigationUpdate Xpro Elementor Addons to the latest version beyond 1.4.4.2 which should contain proper input sanitization. Review all existing content created with the plugin for any injected malicious scripts.

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
Xpro Addons For ElementorWordPress extension
Affected:< 1.4.4.3

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 Xpro Elementor Addons is installed
    Log into WordPress admin, go to Plugins > Installed Plugins, and look for 'Wpxpro Xpro Addons For Elementor' or 'Xpro Elementor Addons' in the list of active plugins.
    Affected if the plugin appears in the installed plugins list
  2. Identify the installed version number
    In the Plugins list, click on the plugin to view details, or check the plugin's main PHP file header for the 'Version' field. Alternatively, use WP-CLI: 'wp plugin list --search=xpro-elementor'
    Affected if the version number displayed is less than 1.4.4.3
  3. Confirm Elementor page builder is active
    Verify that the Elementor page builder plugin is installed and active, as this vulnerability affects content created within the Elementor editor using Xpro addons.
    Affected if Elementor is active and being used to create or edit pages/posts
  4. Inspect content created with Xpro addons
    Review pages and posts that were built with Elementor using Xpro addons. Look for any unexpected script tags, JavaScript event handlers, or suspicious markup in the page source. Check especially for user-submitted content fields that may have been saved.
    Affected if any content contains unsanitized script tags or JavaScript that was injected through user input fields

A user is affected if the Xpro Elementor Addons plugin version is below 1.4.4.3 AND the plugin is installed and actively used with Elementor to create content.

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

Update Xpro Elementor Addons to the latest version beyond 1.4.4.2 which should contain proper input sanitization. Review all existing content created with the plugin for any injected malicious scripts.

Recommended fix High confidence

Xpro Addons For Elementor version 1.4.4.3 or later

  1. 1. Backup your WordPress site and database before performing any updates
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress dashboard
  3. 3. Locate 'Xpro Addons For Elementor' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.4.4.3 or higher
  5. 5. After updating, clear any caching plugins or server-side caches
  6. 6. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins
  7. 7. Test the affected functionality to confirm the Stored XSS vulnerability is remediated

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

Fix this in Xpro Addons For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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