<?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>Sat, 17 Oct 2026 17:53:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-100158 — SQL Chart Builder &lt;= 3.0.6 - Authenticated (Subscriber+) Stored Cross-Site Scripting via SQL Chart Label (X-axis) via S…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-100158</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; elvinhaci SQL Chart Builder&lt;/p&gt;
&lt;p&gt;The SQL Chart Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;X-axis column value ($value-&amp;gt;$xarg_s from $wpdb-&amp;gt;get_results())&amp;#39; parameter in all versions up to, and including, 3.0.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires an administrator to have published a chart whose SQL query returns a column controllable by a lower-privileged user, such as wp_users.display_name, which a Subscriber can populate with a payload via the standard WordPress profile page at /wp-admin/profile.php.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; elvinhaci SQL Chart Builder&lt;/p&gt;
&lt;p&gt;The SQL Chart Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;X-axis column value ($value-&amp;gt;$xarg_s from $wpdb-&amp;gt;get_results())&amp;#39; parameter in all versions up to, and including, 3.0.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires an administrator to have published a chart whose SQL query returns a column controllable by a lower-privileged user, such as wp_users.display_name, which a Subscriber can populate with a payload via the standard WordPress profile page at /wp-admin/profile.php.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-100158</guid>
    </item>
  </channel>
</rss>
