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

CVE-2025-13368

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-04
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 Pricing Widget's 'onClick Event' setting in all versions up to, and including, 1.4.20 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor 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

The Xpro Addons plugin for WordPress fails to properly sanitize and escape user input in the Pricing Widget's onClick Event setting, allowing authenticated contributors and above to inject malicious JavaScript. This stored XSS executes whenever users access pages containing the compromised widget.

MitigationUpdate to version 1.4.21 or later which contains proper input sanitization and output escaping for the onClick Event parameter.

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
    Log in to WordPress admin, navigate to Plugins > Installed Plugins, and locate Xpro Addons in the list. Note the installed version number displayed.
    Affected if The plugin is installed and active.
  2. Confirm plugin version against vulnerable range
    Compare the installed version number to the affected versions (any version prior to the fixed release). The version is visible in the Plugins page or can be checked via FTP in the plugin's main file header.
    Affected if The installed version falls within the vulnerable range.
  3. Identify pages using the Pricing Widget
    Review your WordPress pages and posts for instances where the Xpro Addons Pricing Widget has been added. Check each page editor or use a plugin scanner to list all widget instances.
    Affected if Any page or post contains the Pricing Widget element.
  4. Inspect onClick Event settings for malicious code
    Edit each page containing the Pricing Widget, open the widget settings, and locate the onClick Event field. Examine the stored value for any script tags, javascript: URIs, alert() calls, or other suspicious JavaScript patterns.
    Affected if The onClick Event field contains unsanitized JavaScript code such as <script>, javascript:, or alert().

A user is affected if Xpro Addons is installed with a vulnerable version and any page uses the Pricing Widget with a suspicious onClick Event setting.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 1.4.21 or later which contains proper input sanitization and output escaping for the onClick Event parameter.

Recommended fix Moderate confidence

Version greater than 1.4.20 (latest available version)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate 'Xpro Addons — 140+ Widgets for Elementor'
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, manually download the updated plugin from WordPress.org and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the Pricing Widget's 'onClick Event' setting now properly sanitizes input

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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