dbcve.org
Xpro Addons For ElementorWordPress extension · Wpxpro

CVE-2024-54253

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 1.4.6.2 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 Xpro Xpro Elementor Addons xpro-elementor-addons.This issue affects Xpro Elementor Addons: from n/a through <= 1.4.6.5.

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

A stored Cross-site Scripting (XSS) vulnerability exists in Xpro Elementor Addons plugin for WordPress versions up to 1.4.6.5. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized user inputs that are rendered in web pages, potentially leading to session hijacking or credential theft when administrators or users view the affected content.

MitigationUpgrade to a patched version of Xpro Elementor Addons that includes proper input sanitization and output encoding. Until patched, disable or restrict usage of the affected plugin components and implement Content Security Policy headers.

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.6.2

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. Check installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > Xpro Elementor Addons. The version number is displayed below the plugin name.
    Affected if The displayed version is below 1.4.6.2, meaning the plugin is vulnerable to the unsanitized input flaw.
  2. Verify plugin is active
    In the same plugins list, confirm the Xpro Elementor Addons plugin shows as 'Active'.
    Affected if The plugin is active and serving pages, making the XSS vulnerability reachable.
  3. Identify active Xpro widgets in use
    Go to any Elementor-edited page or template, open the Elementor editor, and check which widgets from the Xpro Addons are present on the page.
    Affected if The page contains Xpro widgets that accept user input (such as forms, buttons, info boxes, or custom content widgets) and render it without proper sanitization.
  4. Inspect stored content for XSS payloads
    Search the wp_posts table in the database, or use a plugin to export/view all page content, and look for script tags, javascript:, onerror=, or other XSS patterns in fields that may have been populated through Xpro widgets.
    Affected if Malicious JavaScript code is found stored in the database, indicating active exploitation of this stored XSS vulnerability.

A user is affected if the Xpro Elementor Addons plugin version is below 1.4.6.2 and the plugin is active with Xpro widgets handling user input on the site.

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.6.2 or later
Fixed in 1.4.6.2
Interim mitigation

Upgrade to a patched version of Xpro Elementor Addons that includes proper input sanitization and output encoding. Until patched, disable or restrict usage of the affected plugin components and implement Content Security Policy headers.

Recommended fix Moderate confidence

Xpro Elementor Addons version 1.4.6.6

  1. 1. Log in to the WordPress admin dashboard where Xpro Addons For Elementor is installed.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate 'Xpro Addons For Elementor' in the plugin list.
  4. 4. Click 'Update now' if an update is available, or manually download version 1.4.6.6 from a trusted source and upload it via Plugins > Add New > Upload Plugin.
  5. 5. After updating, verify the plugin version shows 1.4.6.6 or higher.
  6. 6. Clear any caching mechanisms (page cache, CDN cache) to ensure the patched version is fully deployed.

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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