dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-11614

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The Xpro Addons — 140+ Widgets for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'custom_attributes' parameter in all versions up to, and including, 1.7.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 confidence

Stored XSS vulnerability in the Xpro Addons plugin for WordPress allows authenticated authors+ to inject malicious scripts via the 'custom_attributes' parameter due to insufficient input sanitization and output escaping.

MitigationUpdate the plugin to version 1.7.3 or later when available; otherwise, add proper sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_attr) to the custom_attributes parameter handling.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Addons plugin is installed
    Navigate to WordPress admin > Plugins and locate 'Xpro Addons' or 'Xpro Addons - Elementor Addons' in the installed plugins list
    Affected if Plugin is present and active in the WordPress installation
  2. Check installed plugin version
    In the Plugins list, click on the plugin details to view the installed version number; compare it to the affected range (versions prior to 1.7.3)
    Affected if Installed version is lower than 1.7.3
  3. Identify if custom_attributes feature is in use
    Search WordPress database or theme/builder settings for instances where the 'custom_attributes' parameter is configured; this may appear in Elementor widget settings, theme options, or custom post meta
    Affected if custom_attributes parameter is being used in any widget, post, or template configuration
  4. Review user role permissions
    Check WordPress user roles to determine if any accounts with Author, Editor, or Administrator roles exist; these roles can access the vulnerable parameter
    Affected if There are user accounts with Author-level access or higher who can modify content containing the custom_attributes parameter
  5. Inspect stored data for suspicious scripts
    Query the wp_postmeta table for any records containing custom_attributes values with script tags, event handlers (onclick, onerror, etc.), or iframe/embed tags
    Affected if Malicious script payloads are found stored in the custom_attributes meta values

You are affected if the Xpro Addons plugin is installed with a version below 1.7.3 and any user with Author-level or higher access has used the custom_attributes feature, allowing stored XSS to be present in your database.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.7.3 or later when available; otherwise, add proper sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_attr) to the custom_attributes parameter handling.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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