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

CVE-2026-15096

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 Map Module 'b_width_map' 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 · moderate confidence

The Themify Builder WordPress plugin versions up to 7.7.6 suffer from a stored XSS vulnerability in the Map Module's 'b_width_map' field. Authenticated users with contributor-level permissions or higher can inject arbitrary JavaScript through insufficient input sanitization and output escaping, which executes when other users access the compromised pages.

MitigationUpdate the Themify Builder plugin to a version beyond 7.7.6. Until patched, consider restricting contributor-level user capabilities or deploying a WAF with XSS filtering rules.

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. Identify if Themify Builder plugin is installed
    Locate the Themify Builder plugin directory in the WordPress installation (typically wp-content/plugins/themify-builder/) and read the main plugin file header to obtain the version number.
    Affected if The plugin is installed and the version number is 7.7.6 or lower.
  2. Confirm the installed version against the affected range
    Compare the extracted version number to the affected range (versions up to and including 7.7.6). The version is typically found in the plugin's main PHP file in the 'Version' comment header or the plugin metadata.
    Affected if The installed version is 7.7.6 or any version lower than 7.7.6.
  3. Determine if the Map Module is in use
    Examine WordPress pages, posts, or custom post types that utilize the Themify Builder. Check whether any content has the Map Module element added via the builder interface.
    Affected if The Map Module has been added to any published content.
  4. Inspect the Map Module b_width_map field configuration
    Access the builder editor for a page containing the Map Module. Open the Map Module settings panel and locate the 'b_width_map' field (typically a width/ dimension setting for map elements). Examine the current value stored in this field.
    Affected if The b_width_map field contains HTML, JavaScript, or script-related characters (<, >, javascript:, onload, etc.) that were not intentionally entered by an administrator.
  5. Verify user permission levels on the site
    Review the WordPress user roles present on the site. Specifically identify if there are users with 'Contributor' role or higher (Editor, Author, Administrator) who have access to the Themify Builder editor.
    Affected if Any user with Contributor-level access or higher has the ability to edit content using the Themify Builder.

Your environment is affected if the Themify Builder plugin is installed with version 7.7.6 or lower, the Map Module is used on any content, and users with Contributor permissions or higher can access the builder.

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 a version beyond 7.7.6. Until patched, consider restricting contributor-level user capabilities or deploying a WAF with XSS filtering rules.

Recommended fix Moderate confidence

Themify Builder plugin version 7.7.7 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Themify Builder plugin
  4. 4. Check the current installed version number
  5. 5. If the installed version is 7.7.6 or lower, update the plugin to version 7.7.7 or later
  6. 6. Verify the update completed successfully

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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