CVE-2026-17576: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in revmakx InfiniteWP Client
The InfiniteWP Client plugin for WordPress is vulnerable to SQL Injection via the get_comments action in versions up to, and including, 1.13.9. This is due to insufficient escaping on the array-key names supplied in the JSON request body before use in a SQL statement: IWP_MMB_Comment::get_comments() calls extract() on $args (which silently skips keys that are not valid PHP variable names) but a second foreach($args as $checkbox => $checkbox_val) processes every key, strips the 'iwp_get_comments_' prefix with str_replace(), wraps the remainder in single quotes, and imploded it into an IN(...) clause that is executed via $wpdb->get_results() with no prepare(). Because the request body is read from php://input and JSON-decoded, wp_magic_quotes() never touches the data, so quote characters in keys pass through unaltered. This makes it possible for authenticated attackers, with administrator-level access and above (an administrator can register their own public key via add_site using the plugin's WP-admin-generated activation_key and then issue signed get_comments requests), to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
AI Analysis
Technical Summary
CVE-2026-17576 describes an SQL Injection vulnerability in the InfiniteWP Client plugin for WordPress, affecting versions up to 1.13.9. The issue occurs because the get_comments action processes JSON-decoded input keys without proper escaping before incorporating them into an SQL IN clause. Specifically, the plugin uses extract() on the input array but then iterates over all keys, stripping a prefix and wrapping the remainder in single quotes without using $wpdb->prepare(), leading to unsafe query construction. Since the input is read from php://input and JSON-decoded, it bypasses wp_magic_quotes(), allowing quote characters in keys to pass unaltered. Exploitation requires authenticated administrator-level access, who can register a public key and issue signed get_comments requests to perform SQL Injection and extract sensitive data.
Potential Impact
An attacker with administrator privileges can exploit this vulnerability to execute arbitrary SQL queries via specially crafted JSON request bodies. This can lead to unauthorized disclosure of sensitive database information. The vulnerability does not impact integrity or availability but poses a confidentiality risk.
Mitigation Recommendations
No official patch or fix is currently documented. Administrators should restrict access to trusted users only and monitor for unusual activity. Check the vendor advisory for updates on patches or official remediation. Since this requires administrator-level access, limiting administrative accounts and using strong authentication reduces risk.
CVE-2026-17576: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in revmakx InfiniteWP Client
Description
The InfiniteWP Client plugin for WordPress is vulnerable to SQL Injection via the get_comments action in versions up to, and including, 1.13.9. This is due to insufficient escaping on the array-key names supplied in the JSON request body before use in a SQL statement: IWP_MMB_Comment::get_comments() calls extract() on $args (which silently skips keys that are not valid PHP variable names) but a second foreach($args as $checkbox => $checkbox_val) processes every key, strips the 'iwp_get_comments_' prefix with str_replace(), wraps the remainder in single quotes, and imploded it into an IN(...) clause that is executed via $wpdb->get_results() with no prepare(). Because the request body is read from php://input and JSON-decoded, wp_magic_quotes() never touches the data, so quote characters in keys pass through unaltered. This makes it possible for authenticated attackers, with administrator-level access and above (an administrator can register their own public key via add_site using the plugin's WP-admin-generated activation_key and then issue signed get_comments requests), to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
CVSS v3.1
Score 6.5medium
Affected software
revmakx
InfiniteWP Client
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-17576 describes an SQL Injection vulnerability in the InfiniteWP Client plugin for WordPress, affecting versions up to 1.13.9. The issue occurs because the get_comments action processes JSON-decoded input keys without proper escaping before incorporating them into an SQL IN clause. Specifically, the plugin uses extract() on the input array but then iterates over all keys, stripping a prefix and wrapping the remainder in single quotes without using $wpdb->prepare(), leading to unsafe query construction. Since the input is read from php://input and JSON-decoded, it bypasses wp_magic_quotes(), allowing quote characters in keys to pass unaltered. Exploitation requires authenticated administrator-level access, who can register a public key and issue signed get_comments requests to perform SQL Injection and extract sensitive data.
Potential Impact
An attacker with administrator privileges can exploit this vulnerability to execute arbitrary SQL queries via specially crafted JSON request bodies. This can lead to unauthorized disclosure of sensitive database information. The vulnerability does not impact integrity or availability but poses a confidentiality risk.
Mitigation Recommendations
No official patch or fix is currently documented. Administrators should restrict access to trusted users only and monitor for unusual activity. Check the vendor advisory for updates on patches or official remediation. Since this requires administrator-level access, limiting administrative accounts and using strong authentication reduces risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-07-27T15:27:13.910Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aace1f355bf5e2cf5a3c67e
Added to database: 09/18/2026, 07:02:11 UTC
Last enriched: 09/18/2026, 07:17:34 UTC
Last updated: 09/18/2026, 22:12:52 UTC
Views: 6
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.