CVE-2026-17576
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Exploit Intelligence
EPSS data unavailable for this CVE.
References
Related Vulnerabilities
Other CWE-89 (SQL Injection) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2014-3704 | High | 7.5 | 100% | - | Fix |
| CVE-2015-7297 | High | 7.5 | 100% | - | - |
| CVE-2024-29824 | High | 8.8 | 100% | KEV | Fix |
| CVE-2023-34362 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2019-7481 | High | 7.5 | 100% | KEV + Ransom | Fix |
| CVE-2024-29826 | High | 8.8 | 100% | - | Fix |
Common questions
How do I fix CVE-2026-17576?
No published fix for CVE-2026-17576 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
How severe is CVE-2026-17576?
CVE-2026-17576 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-17576
Markdown
[](https://tridentstack.com/cve/CVE-2026-17576)HTML
<a href="https://tridentstack.com/cve/CVE-2026-17576"><img src="https://tridentstack.com/cve/badge/CVE-2026-17576.svg" alt="CVE-2026-17576"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-18.