{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-17576 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-17576 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-17576 is a medium-severity SQL injection vulnerability in revmakx InfiniteWP Client, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-17576 and fix it if it is affected.\n\nWhat it is: CVE-2026-17576 is a medium-severity SQL injection vulnerability in revmakx InfiniteWP Client, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-17576 in the wild and no public exploit code.\n\nAffected product: revmakx InfiniteWP Client. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-17576/ (Markdown: https://insights.sbomify.com/CVE-2026-17576/index.md)","id":"CVE-2026-17576","markdown":"https://insights.sbomify.com/CVE-2026-17576/index.md","name":"CVE-2026-17576","record":{"aliases":["GHSA-xcfp-7r4f-6367"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated administrators can exploit SQL injection in InfiniteWP Client to extract sensitive database information via crafted JSON requests.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"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 =\u003e $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-\u003eget_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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"InfiniteWP Client \u003c= 1.13.9 - Authenticated (Admin+) SQL Injection via 'iwp_get_comments_*' Array Key","id":"CVE-2026-17576","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"SSL Zen \u003c= 4.7.42 - Reflected Cross-Site Scripting via 'uri' Parameter","id":"CVE-2026-17577"},"packages":[],"prev":{"headline":"NULL Pointer Dereference in HDF5 via Invalid Variable-Length Datatype Type Tag","id":"CVE-2026-17574"},"products":["InfiniteWP Client"],"published":"2026-09-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-18","vendors":["revmakx"]},"summary":"Authenticated administrators can exploit SQL injection in InfiniteWP Client to extract sensitive database information via crafted JSON requests.","url":"https://insights.sbomify.com/CVE-2026-17576/"}