<?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>Mon, 28 Sep 2026 11:44:37 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-15439</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-15439</link>
      <description>&lt;p&gt;The GamiPress plugin for WordPress is vulnerable to authenticated (Subscriber+) SQL Injection via the &amp;#39;q&amp;#39; parameter of the wpForo integration AJAX selector (action gamipress_wpforo_get_posts) in versions up to, and including, 7.9.7. The value is passed only through $wpdb-&amp;gt;esc_like() and interpolated directly into a single-quoted LIKE clause with no %s placeholder. Because esc_like() runs after WordPress core magic quotes, it doubles the injected backslash (\&amp;#39; -&amp;gt; \\&amp;#39;), which MySQL reads as one literal backslash followed by a live closing quote, allowing the attacker to break out of the string and inject boolean-based SQL. The wpForo plugin only needs to be active to register the callback; no wpForo vulnerability is used. Requires a Subscriber account, which can read the gamipress_admin nonce (exposed on every admin page, e.g. /wp-admin/profile.php). Note: the researcher&amp;#39;s Simple:Press vectors (PoC 2 &amp;amp; 3) do not reproduce in current code, which uses $wpdb-&amp;gt;prepare() with %s placeholders; only the wpForo selector is confirmed.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The GamiPress plugin for WordPress is vulnerable to authenticated (Subscriber+) SQL Injection via the &amp;#39;q&amp;#39; parameter of the wpForo integration AJAX selector (action gamipress_wpforo_get_posts) in versions up to, and including, 7.9.7. The value is passed only through $wpdb-&amp;gt;esc_like() and interpolated directly into a single-quoted LIKE clause with no %s placeholder. Because esc_like() runs after WordPress core magic quotes, it doubles the injected backslash (\&amp;#39; -&amp;gt; \\&amp;#39;), which MySQL reads as one literal backslash followed by a live closing quote, allowing the attacker to break out of the string and inject boolean-based SQL. The wpForo plugin only needs to be active to register the callback; no wpForo vulnerability is used. Requires a Subscriber account, which can read the gamipress_admin nonce (exposed on every admin page, e.g. /wp-admin/profile.php). Note: the researcher&amp;#39;s Simple:Press vectors (PoC 2 &amp;amp; 3) do not reproduce in current code, which uses $wpdb-&amp;gt;prepare() with %s placeholders; only the wpForo selector is confirmed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-15439</guid>
    </item>
    <item>
      <title>GHSA-3mqq-vp94-w5r5</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-3mqq-vp94-w5r5</link>
      <description>&lt;p&gt;The GamiPress plugin for WordPress is vulnerable to authenticated (Subscriber+) SQL Injection via the &amp;#39;q&amp;#39; parameter of the wpForo integration AJAX selector (action gamipress_wpforo_get_posts) in versions up to, and including, 7.9.7. The value is passed only through $wpdb-&amp;gt;esc_like() and interpolated directly into a single-quoted LIKE clause with no %s placeholder. Because esc_like() runs after WordPress core magic quotes, it doubles the injected backslash (\&amp;#39; -&amp;gt; \\&amp;#39;), which MySQL reads as one literal backslash followed by a live closing quote, allowing the attacker to break out of the string and inject boolean-based SQL. The wpForo plugin only needs to be active to register the callback; no wpForo vulnerability is used. Requires a Subscriber account, which can read the gamipress_admin nonce (exposed on every admin page, e.g. /wp-admin/profile.php). Note: the researcher&amp;#39;s Simple:Press vectors (PoC 2 &amp;amp; 3) do not reproduce in current code, which uses $wpdb-&amp;gt;prepare() with %s placeholders; only the wpForo selector is confirmed.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The GamiPress plugin for WordPress is vulnerable to authenticated (Subscriber+) SQL Injection via the &amp;#39;q&amp;#39; parameter of the wpForo integration AJAX selector (action gamipress_wpforo_get_posts) in versions up to, and including, 7.9.7. The value is passed only through $wpdb-&amp;gt;esc_like() and interpolated directly into a single-quoted LIKE clause with no %s placeholder. Because esc_like() runs after WordPress core magic quotes, it doubles the injected backslash (\&amp;#39; -&amp;gt; \\&amp;#39;), which MySQL reads as one literal backslash followed by a live closing quote, allowing the attacker to break out of the string and inject boolean-based SQL. The wpForo plugin only needs to be active to register the callback; no wpForo vulnerability is used. Requires a Subscriber account, which can read the gamipress_admin nonce (exposed on every admin page, e.g. /wp-admin/profile.php). Note: the researcher&amp;#39;s Simple:Press vectors (PoC 2 &amp;amp; 3) do not reproduce in current code, which uses $wpdb-&amp;gt;prepare() with %s placeholders; only the wpForo selector is confirmed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-3mqq-vp94-w5r5</guid>
    </item>
  </channel>
</rss>
