https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 08:55:55 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-330221 EUVD-2026-330221 https://cve.radiocsirt.org/vuln/euvd-2026-330221 https://cve.radiocsirt.org/vuln/fkie_cve-2026-9179 <p>The WP Forms Connector plugin for WordPress is vulnerable to SQL Injection via the &#39;order&#39; parameter of the /wp-json/wp/v3/post/list REST endpoint in versions up to and including 1.8. This is due to insufficient escaping on the user-supplied &#39;order&#39; parameter (read directly from $_GET[&#39;order&#39;] into $shorting) and the lack of sufficient preparation on the existing SQL query in the listPost() function, where the value is concatenated unquoted into the ORDER BY clause and executed via $wpdb-&gt;get_results() without $wpdb-&gt;prepare(). The endpoint is registered with permission_callback &#39;__return_true&#39; and performs only a broken header-based check that validates the supplied &#39;Username&#39; corresponds to an administrator account while never verifying the &#39;Password&#39;. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.</p> <p>The WP Forms Connector plugin for WordPress is vulnerable to SQL Injection via the &#39;order&#39; parameter of the /wp-json/wp/v3/post/list REST endpoint in versions up to and including 1.8. This is due to insufficient escaping on the user-supplied &#39;order&#39; parameter (read directly from $_GET[&#39;order&#39;] into $shorting) and the lack of sufficient preparation on the existing SQL query in the listPost() function, where the value is concatenated unquoted into the ORDER BY clause and executed via $wpdb-&gt;get_results() without $wpdb-&gt;prepare(). The endpoint is registered with permission_callback &#39;__return_true&#39; and performs only a broken header-based check that validates the supplied &#39;Username&#39; corresponds to an administrator account while never verifying the &#39;Password&#39;. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-9179 https://cve.radiocsirt.org/vuln/ghsa-rx79-c7q2-h79q <p>The WP Forms Connector plugin for WordPress is vulnerable to SQL Injection via the &#39;order&#39; parameter of the /wp-json/wp/v3/post/list REST endpoint in versions up to and including 1.8. This is due to insufficient escaping on the user-supplied &#39;order&#39; parameter (read directly from $_GET[&#39;order&#39;] into $shorting) and the lack of sufficient preparation on the existing SQL query in the listPost() function, where the value is concatenated unquoted into the ORDER BY clause and executed via $wpdb-&gt;get_results() without $wpdb-&gt;prepare(). The endpoint is registered with permission_callback &#39;__return_true&#39; and performs only a broken header-based check that validates the supplied &#39;Username&#39; corresponds to an administrator account while never verifying the &#39;Password&#39;. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.</p> <p>The WP Forms Connector plugin for WordPress is vulnerable to SQL Injection via the &#39;order&#39; parameter of the /wp-json/wp/v3/post/list REST endpoint in versions up to and including 1.8. This is due to insufficient escaping on the user-supplied &#39;order&#39; parameter (read directly from $_GET[&#39;order&#39;] into $shorting) and the lack of sufficient preparation on the existing SQL query in the listPost() function, where the value is concatenated unquoted into the ORDER BY clause and executed via $wpdb-&gt;get_results() without $wpdb-&gt;prepare(). The endpoint is registered with permission_callback &#39;__return_true&#39; and performs only a broken header-based check that validates the supplied &#39;Username&#39; corresponds to an administrator account while never verifying the &#39;Password&#39;. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.</p> https://cve.radiocsirt.org/vuln/ghsa-rx79-c7q2-h79q