<?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://vulnerability.circl.lu</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, 13 Oct 2026 21:04:06 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-3362</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-3362</link>
      <description>&lt;p&gt;The Short Comment Filter plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;Minimum Count&amp;#39; settings field in all versions up to and including 2.2. This is due to insufficient input sanitization (no sanitize callback on register_setting) and missing output escaping (no esc_attr() on the echoed value in the input&amp;#39;s value attribute). The option value is stored via update_option() and rendered unescaped in an HTML attribute context. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in the settings page that will execute whenever a user accesses that page. This is particularly impactful in WordPress multisite installations or when DISALLOW_UNFILTERED_HTML is set, where administrators are not granted the unfiltered_html capability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Short Comment Filter plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;Minimum Count&amp;#39; settings field in all versions up to and including 2.2. This is due to insufficient input sanitization (no sanitize callback on register_setting) and missing output escaping (no esc_attr() on the echoed value in the input&amp;#39;s value attribute). The option value is stored via update_option() and rendered unescaped in an HTML attribute context. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in the settings page that will execute whenever a user accesses that page. This is particularly impactful in WordPress multisite installations or when DISALLOW_UNFILTERED_HTML is set, where administrators are not granted the unfiltered_html capability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-3362</guid>
    </item>
    <item>
      <title>GHSA-39pg-69jq-6vx9</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-39pg-69jq-6vx9</link>
      <description>&lt;p&gt;The Short Comment Filter plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;Minimum Count&amp;#39; settings field in all versions up to and including 2.2. This is due to insufficient input sanitization (no sanitize callback on register_setting) and missing output escaping (no esc_attr() on the echoed value in the input&amp;#39;s value attribute). The option value is stored via update_option() and rendered unescaped in an HTML attribute context. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in the settings page that will execute whenever a user accesses that page. This is particularly impactful in WordPress multisite installations or when DISALLOW_UNFILTERED_HTML is set, where administrators are not granted the unfiltered_html capability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Short Comment Filter plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;Minimum Count&amp;#39; settings field in all versions up to and including 2.2. This is due to insufficient input sanitization (no sanitize callback on register_setting) and missing output escaping (no esc_attr() on the echoed value in the input&amp;#39;s value attribute). The option value is stored via update_option() and rendered unescaped in an HTML attribute context. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in the settings page that will execute whenever a user accesses that page. This is particularly impactful in WordPress multisite installations or when DISALLOW_UNFILTERED_HTML is set, where administrators are not granted the unfiltered_html capability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-39pg-69jq-6vx9</guid>
    </item>
  </channel>
</rss>
