CVE-2026-18881

TableOn <= 1.0.5.1 - Unauthenticated Blind SQL Injection via 'comment_count' Filter Parameter

Published Aug 5, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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).

Analysis

AI-generated

Technical impact

The vulnerability is an unvalidated type of blind SQL injection in the TableOn – WordPress Posts Table Filterable plugin. The flaw occurs when the public AJAX endpoint processes the filter_data[comment_count] value without proper sanitization or preparation, allowing attackers to inject additional SQL fragments. Because the injection is blind, the attacker can discover sensitive database details such as database name, user credentials, or other site content, resulting in unauthorized data exposure. This flaw is categorized under CWE‑89, representing SQL injection weaknesses.

Affected Systems

This issue affects installations of the TableOn – WordPress Posts Table Filterable plugin for WordPress versions up to and including 1.0.5.1. The vendor, realmag777, enumerated this as a WordPress plugin. No specific WordPress core or additional vendor is affected beyond the plugin itself.

Risk and Exploitability

With a CVSS score of 7.5, the severity falls into the high‑risk range, indicating that the vulnerability could have serious consequences for confidentiality and integrity. No EPSS value is available, so the likely exploitation probability is unknown; however, the attack can be performed unauthenticated via a public AJAX action, meaning that any internet‑reachable site running the vulnerable plugin could be targeted. The vulnerability is not listed in the CISA KEV catalog, but its high score and unauthenticated nature suggest that threat actors may already be probing affected sites.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade TableOn – WordPress Posts Table Filterable to version 1.0.6 or later.
  • If an upgrade is not immediately possible, temporarily disable the plugin or remove the public AJAX endpoint to block unauthenticated access to the vulnerable function.
  • Ensure any remaining instances of filter_data[comment_count] are sanitized by replacing raw string interpolation with $wpdb->prepare or intval casting before use in SQL queries.
  • Verify that the plugin no longer exposes the vulnerable AJAX action, and monitor logs for any suspicious activity.

Generated by OpenCVE AI on August 5, 2026 at 08:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Realmag777
Realmag777 tableon – Wordpress Posts Table Filterable
Wordpress
Wordpress wordpress
Vendors & Products Realmag777
Realmag777 tableon – Wordpress Posts Table Filterable
Wordpress
Wordpress wordpress
Type Values Removed Values Added
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).
Title TableOn <= 1.0.5.1 - Unauthenticated Blind SQL Injection via 'comment_count' Filter Parameter
Weaknesses CWE-89
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Sources

Status
PUBLISHED
Assigner
Wordfence
Published
Updated
Aug 5, 2026, 1:29 PM
Reserved
Aug 4, 2026, 6:28 PM
Status
Deferred
Published
Aug 5, 2026, 8:16 AM
Modified
Aug 12, 2026, 9:00 PM