Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-13535

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-01

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

NVD · unedited

The King Addons for Elementor plugin for WordPress is vulnerable to multiple Contributor+ DOM-Based Stored Cross-Site Scripting vulnerabilities in all versions up to, and including, 51.1.38. This is due to insufficient input sanitization and output escaping across multiple widgets and features. The plugin uses esc_attr() and esc_url() within JavaScript inline event handlers (onclick attributes), which allows HTML entities to be decoded by the DOM, enabling attackers to break out of the JavaScript context. Additionally, several JavaScript files use unsafe DOM manipulation methods (template literals, .html(), and window.location.href with unvalidated URLs) with user-controlled data. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts via Elementor widget settings that execute when a user accesses the injected page or when an administrator previews the page in Elementor's editor. The vulnerability was partially patched in version 5.1.51.

Technical summary

dbcve analysis · high confidence

The King Addons for Elementor plugin for WordPress is vulnerable to multiple DOM-Based Stored Cross-Site Scripting (XSS) vulnerabilities in versions up to 51.1.38. Authenticated attackers with Contributor-level access can inject arbitrary JavaScript via Elementor widget settings. The vulnerability stems from improper use of esc_attr() and esc_url() in JavaScript inline event handlers (onclick attributes), where HTML entities are decoded by the DOM, enabling attackers to break out of the JavaScript context. Additionally, unsafe DOM manipulation methods (template literals, .html(), and window.location.href) in JavaScript files process user-controlled data without validation.

MitigationUpdate the King Addons for Elementor plugin to version 5.1.51 or later. Review all Elementor pages and templates that use this plugin for any malicious injections, and ensure Contributor+ users follow the principle of least privilege regarding plugin access.

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

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify King Addons for Elementor is installed

In WordPress admin, go to Plugins > Installed Plugins and look for 'King Addons for Elementor' or check the plugin files for version information in the main plugin file header

Affected if The plugin is installed and the version is 51.1.38 or lower
Confirm the installed version number

Access the plugin version directly via WordPress admin Plugins page, or inspect the main plugin PHP file (typically king-addons-for-elementor.php) and locate the 'Version' header comment

Affected if Version is 51.1.38 or any version up to and including 51.1.38 (versions prior to 5.1.51)
Determine if Elementor Page Builder is active

Check if Elementor is installed and active in WordPress under Plugins > Installed Plugins, as this vulnerability is exploited through Elementor widget settings

Affected if Elementor is active and in use on the site
Audit Elementor pages and templates using King Addons widgets

Review Elementor pages, posts, and templates that include King Addons widgets. Inspect the widget settings for any unusual onclick attributes or script injections in custom URLs, links, or button widgets

Affected if Any Elementor content contains injected JavaScript in widget settings, particularly in fields that generate onclick attributes or use template literals, .html(), or window.location.href
Check for Contributor-level or higher user accounts

In WordPress admin, go to Users > All Users and review the list of users with Contributor, Author, Editor, or Administrator roles

Affected if There are user accounts with Contributor-level access or higher who have access to Elementor editing capabilities

You are affected if King Addons for Elementor is installed with version 51.1.38 or lower, Elementor is active, and Contributor+ users can edit Elementor content that may contain injected scripts in widget settings.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update the King Addons for Elementor plugin to version 5.1.51 or later. Review all Elementor pages and templates that use this plugin for any malicious injections, and ensure Contributor+ users follow the principle of least privilege regarding plugin access.

Recommended fix Moderate confidence

Latest version of King Addons for Elementor (version 5.1.51 or higher, as 5.1.51 contains the partial patch)

1. Back up your WordPress site and database before making any changes.
2. Navigate to WordPress Dashboard > Plugins > Installed Plugins.
3. Locate 'King Addons for Elementor' in the plugin list.
4. If the plugin is not already at version 5.1.51 or higher, click 'Update Now' to install the latest available version.
5. After updating, clear any caching plugins or server-side caches.
6. Verify the update was successful by checking the plugin version in the Plugins list.
7. For sites using the Elementor editor, test previewing pages with custom widget settings to confirm functionality.

Caveat Minor: Review any widget customizations after upgrade as JavaScript context handling has changed for security

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

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing3.0 h
Review / QA2.0 h

11.0 hours of engineering $1,930

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13535 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-13535?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 6.4 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

Need this fixed?

Have this fixed 11 hrs · Moderate

Typical engagement from $1,930

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-13535 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References