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

CVE-2026-15097

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-11
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 Themify Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'height_slider' Slider Module Field in all versions up to, and including, 7.7.6 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 Themify Builder WordPress plugin fails to properly sanitize and escape the 'height_slider' parameter in the Slider Module, allowing authenticated users with contributor-level access or higher to inject malicious JavaScript. This stored XSS executes whenever the affected page is accessed by other users.

MitigationUpdate the Themify Builder plugin to version 7.7.7 or later, which includes proper input sanitization and output escaping for the height_slider field. Until then, restrict contributor-level user permissions and audit existing content for injected scripts.

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 Themify Builder plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Themify Builder' in the list. Note the installed version number displayed there.
    Affected if The plugin is present and the version shown is below 7.7.7 (e.g., 7.7.6, 7.7.0, etc.) or if no version is displayed at all.
  2. Identify if the Slider Module is in use
    Navigate to Pages or Posts in the WordPress admin. Edit any page that may have been created using the Themify Builder. In the builder interface, check if a Slider Module has been added to any of the pages.
    Affected if The Slider Module has been added to any published or draft content in the site.
  3. Inspect the height_slider parameter in existing content
    If using a database query tool, examine the postmeta or content tables for any entries containing 'height_slider' that may contain unsanitized script tags or unusual attribute values. Alternatively, edit any page with a Slider Module and check the Slider Module settings for the height_slider field.
    Affected if The height_slider value contains unescaped HTML, JavaScript tags, or event handlers (onclick, onerror, etc.).
  4. Review user roles with contributor access
    In WordPress admin, go to Users > All Users and review the role assigned to each user. Identify users with 'Contributor', 'Author', 'Editor', or 'Administrator' roles.
    Affected if Any user with Contributor-level or higher access exists in the WordPress installation.

A user is affected if the Themify Builder plugin is installed with a version below 7.7.7 AND the Slider Module is in use AND at least one user with contributor-level or higher access exists in WordPress.

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 Themify Builder plugin to version 7.7.7 or later, which includes proper input sanitization and output escaping for the height_slider field. Until then, restrict contributor-level user permissions and audit existing content for injected scripts.

Recommended fix Moderate confidence

Themify Builder version 7.7.7 or later (latest stable release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Themify Builder plugin
  4. Check if current version is 7.7.6 or earlier
  5. If vulnerable, click 'Update Now' to upgrade to the latest version
  6. Verify the update completed successfully
  7. Test the Slider Module functionality to ensure the plugin still works correctly after the update

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

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-15097 — 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-15097 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