<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>TableOn – WordPress Posts Table Filterable (&lt;= 1.0.5.1) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/tableon--wordpress-posts-table-filterable--1.0.5.1/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 05 Aug 2026 11:15:39 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/tableon--wordpress-posts-table-filterable--1.0.5.1/feed.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-18881: SQL Injection in TableOn WordPress Plugin</title><link>https://feed.craftedsignal.io/briefs/2026-08-tableon-sqli/</link><pubDate>Wed, 05 Aug 2026 11:15:39 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-tableon-sqli/</guid><description>An unauthenticated SQL injection vulnerability in the TableOn WordPress plugin allows attackers to extract sensitive database information via the filter_data[comment_count] parameter.</description><content:encoded><![CDATA[<p>The TableOn - WordPress Posts Table Filterable plugin for WordPress is vulnerable to a blind SQL injection vulnerability identified as CVE-2026-18881. This flaw affects all versions up to and including 1.0.5.1. The vulnerability exists within the public <code>tableon_get_table_data</code> AJAX action, specifically due to improper handling of the <code>filter_data[comment_count]</code> parameter. The plugin fails to apply necessary input validation or sanitization, such as <code>intval()</code> casting, and fails to use the <code>$wpdb-&gt;prepare()</code> function when processing this parameter. Consequently, the input is interpolated directly into a <code>posts_where</code> SQL clause after being split by a colon delimiter. Unauthenticated attackers can leverage this flaw to append malicious SQL commands, enabling them to execute blind SQL injection attacks to exfiltrate sensitive data from the WordPress database, including entries from the <code>wp_users</code> table.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated remote attackers to perform blind SQL injection against the host WordPress site. Potential consequences include the exfiltration of sensitive information, such as administrator hashes or user credentials, which could lead to complete site compromise. Given the prevalence of WordPress plugins in enterprise environments, this poses a high risk to sites utilizing the TableOn plugin.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the TableOn - WordPress Posts Table Filterable plugin to the latest version released after August 5, 2026, which contains the security patch for CVE-2026-18881.</li>
<li>Implement a Web Application Firewall (WAF) rule to inspect and block incoming HTTP requests targeting the <code>tableon_get_table_data</code> action where the <code>filter_data[comment_count]</code> parameter contains SQL-specific characters or patterns.</li>
<li>Audit database query logs for suspicious patterns originating from external IP addresses targeting the affected AJAX endpoint.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>