CVE-2026-17576 revmakx · InfiniteWP Client

InfiniteWP Client <= 1.13.9 - Authenticated (Admin+) SQL Injection via 'iwp_get_comments_*' Array Key

Vulnerability at a glance

Severity, exploitation likelihood & attack requirements

CVSS v3.1 severity
6.5Medium
EPSS · exploitation likelihood
Not available No score available FIRST
Known exploitation
Not in KEV CISA KEV catalog Absence does not establish safety
Attack vector
NetworkRemotely reachable
Attack complexity
LowFewer obstacles to exploitation
Privileges required
LowBasic privileges required
User interaction
NoneNo user action needed
Exploit availability & maturity
Not scored Availability not established No explicit exploit maturity assessment View exploit evidence
Already protected by existing Atomicorp rules No new CVE-specific rule required.

Atomicorp ModSecurity protection

Protected by Atomicorp rules

Atomicorp ModSecurity rules block attacks exploiting this vulnerability when blocking is enabled. Keep your rules current.

By targeting underlying attack techniques and CWE weakness classes, existing rules can protect against newly disclosed vulnerabilities. Rule changes are regression-tested against attack and false-positive corpora.

6 rules identified Verified 2026-09-18 View rules & research details →

WAF protection applies to the tested attack paths; it does not change the CVSS or EPSS score. Keep your software patched and your Atomicorp rules current.

CISA SSVC

No CISA SSVC assessment is available in the current source data.

On this page

CVE Details

  • Protection status: Protected by Atomicorp rules · About protection statuses
  • CVE: CVE-2026-17576
  • Name: InfiniteWP Client <= 1.13.9 - Authenticated (Admin+) SQL Injection via ‘iwp_get_comments_*’ Array Key
  • Severity: Medium
  • CVSS: 6.5 (v3.1) (Medium)
  • CVSS version: 3.1
  • CVSS source: Wordfence CNA
  • CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
    • Attack vector: Network
    • Attack complexity: Low
    • Privileges required: Low
    • User interaction: None
    • Scope: Unchanged
    • Confidentiality impact: High
    • Integrity impact: None
    • Availability impact: None
  • CWE: CWE-89
  • Vendor: revmakx
  • Vulnerable product: InfiniteWP Client
  • CVE published: 2026-09-18
  • CVE last modified: 2026-09-18
  • Latest Update: 2026-09-18
  • Selected Rule IDs observed: 340017 , 340144 , 340156 , 360147 , 360148 , 380122
  • Matching rules: 6; rules with blocking actions: 6
  • Would-block Rule IDs: 340017 , 340144 , 340156 , 360147 , 360148 , 380122
  • Request surfaces inspected: JSON request data, Request URI, Request argument names, Request arguments, Request cookies, Request headers, SOAP request data, XML request data
Technical vulnerability details · CVSS assessments, exploit evidence & CPE data

CVSS assessments

CVSS v3.1 · security@wordfence.com

  • Base score: 6.5
  • Base severity: MEDIUM
  • Exploitability subscore: 2.8
  • Impact subscore: 3.6
  • Assessment type: Primary
  • Source identifier: security@wordfence.com
  • Full vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
    • Attack vector: Network
    • Attack complexity: Low
    • Privileges required: Low
    • User interaction: None
    • Scope: Unchanged
    • Confidentiality impact: High
    • Integrity impact: None
    • Availability impact: None
  • Exploit maturity: Not scored

Exploitability and impact subscores describe the vulnerability’s technical characteristics. Exploit maturity describes the reported state of exploitation; these are separate measures.

Assessment source: NVD record · CVE record

Vulnerable CPE configurations

No vulnerable CPE configurations are supplied in the current NVD record. See the affected-product information and vendor guidance on this page.

Vulnerability 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.

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (340017 , 340144 , 340156 , 360147 , 360148 , 380122 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

    • Affected versions: revmakx InfiniteWP Client versions through 1.13.9.
    • No specific CNA/vendor solution or workaround is included in the current CVE Record . Review the vendor’s security advisories and supported-release guidance before making changes.

  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

  • Source: Atomicorp AI Research Framework
  • Tags: cve, derived, sqli, waf-probe

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ .