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

CVE-2026-15285

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-10
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 6 weeks old

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 Plus Addons for Elementor plugin for WordPress was vulnerable to Authenticated (Contributor+) Stored Cross-Site Scripting via the Button widget's `custom_attributes` setting in versions up to and including 6.4.11. The `render` function in `modules/widgets/tp_button.php` passed the raw `custom_attributes` string through `tp_senitize_js_input()`. This filter is bypassable. The issue is patched in version 6.4.12.

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 Plus Addons for Elementor plugin versions up to 6.4.11 contained a stored XSS vulnerability in the Button widget's custom_attributes parameter. The render function in tp_button.php passed user-supplied custom_attributes through the tp_senitize_js_input() filter, which could be bypassed, allowing authenticated users with Contributor+ permissions to inject malicious JavaScript that persists in the page.

MitigationUpdate the Plus Addons for Elementor plugin to version 6.4.12 or later to patch the sanitization bypass. If immediate update is not possible, consider restricting Contributor-level access or disabling the Button widget until the patch can be applied.

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. Confirm Plus Addons for Elementor is installed
    Navigate to WordPress admin > Plugins and locate 'Plus Addons for Elementor' in the plugin list
    Affected if Plugin is not installed on the WordPress site
  2. Check installed plugin version
    In the Plugins list, view the version column for Plus Addons for Elementor, or check the plugin header in /wp-content/plugins/the-plus-addons-for-elementor/readme.txt
    Affected if Version is 6.4.11 or lower (versions 6.4.12 and later are patched)
  3. Identify use of Button widget with custom_attributes
    Search page/post content or Elementor templates for instances of the Plus Button widget. In the widget settings panel, expand the Custom Attributes field to see if any custom attributes are configured
    Affected if Button widget is in use and custom_attributes parameter contains user-supplied values
  4. Inspect saved content for injected JavaScript
    Export or view the raw content of pages/posts containing the Plus Button widget. Search for <script> tags, javascript: URLs, or event handlers (onclick, onerror, onload) within the custom_attributes values stored in postmeta or elementor data
    Affected if Unexpected script tags or event handler attributes are present in custom_attributes values in the database

Your site is affected if Plus Addons for Elementor version 6.4.11 or lower is installed AND the Button widget with custom_attributes is being used, as authenticated attackers could have injected persistent JavaScript.

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 the Plus Addons for Elementor plugin to version 6.4.12 or later to patch the sanitization bypass. If immediate update is not possible, consider restricting Contributor-level access or disabling the Button widget until the patch can be applied.

Recommended fix High confidence

6.4.12

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Plus Addons for Elementor' plugin
  4. Click 'Update Now' to update to the latest version, or manually upload version 6.4.12
  5. Verify the plugin is running version 6.4.12 after update

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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