CVE-2026-17576

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-09-18. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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
6.5
EG Score
6.5MEDIUMhigh confidence
EG Risk
29
EG Risk 29/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 18, 2026

Last Modified

September 18, 2026

Vendor Advisories for CVE-2026-17576(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 03:44 UTCEG score recompute
  2. 2026-10-05 03:44 UTCGHSA enrichment
  3. 2026-10-04 23:21 UTCEPSS rescore
  4. 2026-10-04 01:20 UTCEG score recompute
  5. 2026-10-04 01:20 UTCGHSA enrichment
  6. 2026-10-03 14:25 UTCEPSS rescore
  7. 2026-10-02 22:57 UTCEG score recompute
  8. 2026-10-02 22:57 UTCGHSA enrichment
  9. 2026-10-01 20:32 UTCEG score recompute
  10. 2026-10-01 20:32 UTCGHSA enrichment
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-09-30 18:02 UTCEG score recompute
  13. 2026-09-30 18:02 UTCGHSA enrichment
  14. 2026-09-30 15:02 UTCEPSS rescore
  15. 2026-09-29 15:32 UTCEG score recompute
  16. 2026-09-29 15:32 UTCGHSA enrichment
  17. 2026-09-29 15:20 UTCEPSS rescore
  18. 2026-09-28 13:51 UTCEPSS rescore
  19. 2026-09-28 13:09 UTCEG score recompute
  20. 2026-09-28 13:09 UTCGHSA enrichment
  21. 2026-09-27 13:47 UTCEPSS rescore
  22. 2026-09-27 10:45 UTCEG score recompute
  23. 2026-09-27 10:45 UTCGHSA enrichment
  24. 2026-09-26 15:58 UTCEPSS rescore
  25. 2026-09-26 08:14 UTCEG score recompute
Show 22 more
  1. 2026-09-26 08:14 UTCGHSA enrichment
  2. 2026-09-25 05:47 UTCEG score recompute
  3. 2026-09-25 05:47 UTCGHSA enrichment
  4. 2026-09-24 03:24 UTCEG score recompute
  5. 2026-09-24 03:24 UTCGHSA enrichment
  6. 2026-09-23 01:00 UTCEG score recompute
  7. 2026-09-23 01:00 UTCGHSA enrichment
  8. 2026-09-21 22:36 UTCEG score recompute
  9. 2026-09-21 22:36 UTCGHSA enrichment
  10. 2026-09-20 20:13 UTCGHSA enrichment
  11. 2026-09-19 17:49 UTCEG score recompute
  12. 2026-09-19 17:49 UTCGHSA enrichment
  13. 2026-09-18 19:27 UTCEPSS rescore
  14. 2026-09-18 15:25 UTCEG score recompute
  15. 2026-09-18 15:25 UTCGHSA enrichment
  16. 2026-09-18 14:34 UTCEG score recompute
  17. 2026-09-18 14:34 UTCGHSA enrichment
  18. 2026-09-18 13:39 UTCEG score recompute
  19. 2026-09-18 13:39 UTCGHSA enrichment
  20. 2026-09-18 07:24 UTCEG score recompute
  21. 2026-09-18 06:59 UTCEG score recompute
  22. 2026-09-18 06:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-17576?
CVE-2026-17576 is a medium vulnerability published on September 18, 2026. The InfiniteWP Client plugin for WordPress is vulnerable to SQL Injection via the getcomments 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: IWPMMBComment::getcomments()…
When was CVE-2026-17576 disclosed?
CVE-2026-17576 was first published on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17576 actively exploited?
CVE-2026-17576 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17576?
CVE-2026-17576 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-17576?
No fix for CVE-2026-17576 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-17576 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-17576

Explore →

Is Your Infrastructure Affected by CVE-2026-17576?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.