<?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, 29 Sep 2026 19:24:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-6295 — WP Optimizer &lt;= 2.5.0 - Authenticated (Administrator+) SQL Injection via 's' Parameter</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-6295</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; sh1zen WP Optimizer – PageSpeed, Cache, Minify &amp;amp; Core Web Vitals&lt;/p&gt;
&lt;p&gt;The WP Optimizer plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;s&amp;#39; parameter in all versions up to and including 2.5.0. This is due to an unsafe subquery-detection branch in the Query::parse_key_compare_field() method that, when the user-supplied value matches the regex ^[(\s]*SELECT\s+, wraps the value in parentheses and embeds it directly into the SQL string without any escaping or quoting. While the normal LIKE code path correctly uses esc_sql($wpdb-&amp;gt;esc_like(...)) and wraps the value in single quotes, this branch completely bypasses those protections. Because the attack payload (SELECT ...) contains no single quotes, WordPress&amp;#39;s wp_magic_quotes() provides no protection. This makes it possible for authenticated attackers with administrator-level access to inject arbitrary SQL subqueries — including time-based blind payloads — that can be used to extract sensitive information from the database.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; sh1zen WP Optimizer – PageSpeed, Cache, Minify &amp;amp; Core Web Vitals&lt;/p&gt;
&lt;p&gt;The WP Optimizer plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;s&amp;#39; parameter in all versions up to and including 2.5.0. This is due to an unsafe subquery-detection branch in the Query::parse_key_compare_field() method that, when the user-supplied value matches the regex ^[(\s]*SELECT\s+, wraps the value in parentheses and embeds it directly into the SQL string without any escaping or quoting. While the normal LIKE code path correctly uses esc_sql($wpdb-&amp;gt;esc_like(...)) and wraps the value in single quotes, this branch completely bypasses those protections. Because the attack payload (SELECT ...) contains no single quotes, WordPress&amp;#39;s wp_magic_quotes() provides no protection. This makes it possible for authenticated attackers with administrator-level access to inject arbitrary SQL subqueries — including time-based blind payloads — that can be used to extract sensitive information from the database.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-6295</guid>
    </item>
  </channel>
</rss>
