CVE-2026-18881: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in realmag777 TableOn – WordPress Posts Table Filterable
The TableOn – WordPress Posts Table Filterable plugin for WordPress is vulnerable to blind SQL Injection via the `filter_data[comment_count]` parameter of the public `tableon_get_table_data` AJAX action in all versions up to, and including, 1.0.5.1. This is due to insufficient escaping on the user-supplied parameter and lack of sufficient preparation on the existing SQL query — the value is split on `:` and both halves are interpolated directly into a `posts_where` SQL clause without `intval()` casting or `$wpdb->prepare()`. This makes it possible for unauthenticated attackers to append additional SQL queries into the already-existing query that can be used to extract sensitive information from the database (researcher demonstrated extraction of database(), wp_users.user_login, and wp_users.user_pass).
AI Analysis
Technical Summary
CVE-2026-18881 describes a blind SQL Injection vulnerability in the TableOn – WordPress Posts Table Filterable plugin for WordPress. The flaw exists in the handling of the filter_data[comment_count] parameter within the tableon_get_table_data AJAX action. The plugin splits the parameter value on a colon and interpolates both parts directly into a posts_where SQL clause without applying intval() casting or using $wpdb->prepare(). This improper neutralization of special elements in the SQL command enables unauthenticated attackers to append additional SQL queries, demonstrated by extraction of database names and user credentials.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to perform blind SQL Injection attacks, potentially extracting sensitive information such as database names and user login credentials from the WordPress database. The CVSS score of 7.5 (high) reflects the network attack vector, low attack complexity, no privileges required, and high confidentiality impact. There is no impact on integrity or availability reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch is currently available. Until a patch is released, users should consider disabling the vulnerable AJAX action or restricting access to it as a temporary mitigation. Avoid exposing the filter_data[comment_count] parameter to untrusted users.
CVE-2026-18881: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in realmag777 TableOn – WordPress Posts Table Filterable
Description
The TableOn – WordPress Posts Table Filterable plugin for WordPress is vulnerable to blind SQL Injection via the `filter_data[comment_count]` parameter of the public `tableon_get_table_data` AJAX action in all versions up to, and including, 1.0.5.1. This is due to insufficient escaping on the user-supplied parameter and lack of sufficient preparation on the existing SQL query — the value is split on `:` and both halves are interpolated directly into a `posts_where` SQL clause without `intval()` casting or `$wpdb->prepare()`. This makes it possible for unauthenticated attackers to append additional SQL queries into the already-existing query that can be used to extract sensitive information from the database (researcher demonstrated extraction of database(), wp_users.user_login, and wp_users.user_pass).
CVSS v3.1
Score 7.5high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-18881 describes a blind SQL Injection vulnerability in the TableOn – WordPress Posts Table Filterable plugin for WordPress. The flaw exists in the handling of the filter_data[comment_count] parameter within the tableon_get_table_data AJAX action. The plugin splits the parameter value on a colon and interpolates both parts directly into a posts_where SQL clause without applying intval() casting or using $wpdb->prepare(). This improper neutralization of special elements in the SQL command enables unauthenticated attackers to append additional SQL queries, demonstrated by extraction of database names and user credentials.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to perform blind SQL Injection attacks, potentially extracting sensitive information such as database names and user login credentials from the WordPress database. The CVSS score of 7.5 (high) reflects the network attack vector, low attack complexity, no privileges required, and high confidentiality impact. There is no impact on integrity or availability reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch is currently available. Until a patch is released, users should consider disabling the vulnerable AJAX action or restricting access to it as a temporary mitigation. Avoid exposing the filter_data[comment_count] parameter to untrusted users.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-08-04T18:28:16.502Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a72e5c6bf8831d539734f28
Added to database: 08/05/2026, 07:27:02 UTC
Last enriched: 08/05/2026, 07:56:35 UTC
Last updated: 08/06/2026, 00:41:11 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.