<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 10 Nov 2026 06:31:23 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-115869</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-115869</link>
      <description>&lt;p&gt;The Themify Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;variations&amp;#39; 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 &amp;#39;textbox&amp;#39; or &amp;#39;textarea&amp;#39;, so the &amp;#39;repeater&amp;#39; 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 &amp;lt;style&amp;gt; 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).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Themify Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;variations&amp;#39; 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 &amp;#39;textbox&amp;#39; or &amp;#39;textarea&amp;#39;, so the &amp;#39;repeater&amp;#39; 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 &amp;lt;style&amp;gt; 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).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-115869</guid>
    </item>
    <item>
      <title>GHSA-2m93-9jp5-xhh2</title>
      <link>https://db.gcve.eu/vuln/ghsa-2m93-9jp5-xhh2</link>
      <description>&lt;p&gt;The Themify Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;variations&amp;#39; 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 &amp;#39;textbox&amp;#39; or &amp;#39;textarea&amp;#39;, so the &amp;#39;repeater&amp;#39; 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 &amp;lt;style&amp;gt; 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).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Themify Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;variations&amp;#39; 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 &amp;#39;textbox&amp;#39; or &amp;#39;textarea&amp;#39;, so the &amp;#39;repeater&amp;#39; 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 &amp;lt;style&amp;gt; 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).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-2m93-9jp5-xhh2</guid>
    </item>
  </channel>
</rss>
