HomeWordPress vulnerabilitiesInfiniteWP Client
InfiniteWP Client vulnerabilities
InfiniteWP Client has 6 known vulnerabilities in this database. The most recent published record is dated 18 Sep 2026.
- Known vulnerabilities
- 6
- Active installs
- 200,000+
- Latest version
- 1.13.10
- Last updated
- 19 Aug 2026
- Most recent
- 18 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| SQL injection CVE-2026-17576 | Medium 6.5 | Up to 1.13.9 | Fixed in a later version (latest 1.13.10) | 18 Sep 2026 |
| Remote code execution CVE-2026-15038 | Critical 9.8 | Before 1.13.6 | Fixed in 1.13.6 | 9 Aug 2026 |
| Path traversal CVE-2024-10585 | Medium 5.3 | Before 1.13.1 | Fixed in 1.13.1 | 8 Jan 2025 |
| Sensitive data exposure CVE-2023-6565 | Medium 5.9 | Before 1.12.3.1 | Fixed in 1.12.3.1 | 29 Feb 2024 |
| Sensitive data exposure CVE-2023-2916 | High 7.5 | Before 1.12.1 | Fixed in 1.12.1 | 15 Aug 2023 |
| Broken access control CVE-2020-8772 | Critical 9.8 | Before 1.9.4.5 | Fixed in 1.9.4.5 | 6 Feb 2020 |
Read the published descriptions
- CVE-2026-17576, 18 Sep 2026
- 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. CVE record
- CVE-2026-15038, 9 Aug 2026
- The InfiniteWP Client WordPress plugin before 1.13.6 does not properly verify the site-connection state and the authenticity of requests to its remote-management endpoint on WordPress Multisite installations, allowing unauthenticated attackers to bind their own key, hijack an administrator session, and take over the entire network, leading to remote code execution. CVE record
- CVE-2024-10585, 8 Jan 2025
- The InfiniteWP Client plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.13.0 via the 'historyID' parameter of the ~/debug-chart/index.php file. This makes it possible for unauthenticated attackers to read .txt files outside of the intended directory. CVE record
- CVE-2023-6565, 29 Feb 2024
- The InfiniteWP Client plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.12.3 via the multi-call backup option. This makes it possible for unauthenticated attackers to extract sensitive data from a temporary SQL file via repeated GET requests during the limited time window of the backup process. CVE record
- CVE-2023-2916, 15 Aug 2023
- The InfiniteWP Client plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 1.11.1 via the 'admin_notice' function. This can allow authenticated attackers with subscriber-level permissions or above to extract sensitive data including configuration. It can only be exploited if the plugin has not been configured yet. If combined with another arbitrary plugin installation and activation vulnerability, it may be possible to connect a site to InfiniteWP which would make remote management possible and allow for elevation of privileges. CVE record
- CVE-2020-8772, 6 Feb 2020
- The InfiniteWP Client plugin before 1.9.4.5 for WordPress has a missing authorization check in iwp_mmb_set_request in init.php. Any attacker who knows the username of an administrator can log in. CVE record
What to do if you run InfiniteWP Client
If you run InfiniteWP Client, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new InfiniteWP Client vulnerabilities
Free. We email you when a new vulnerability is published for InfiniteWP Client, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.