CVE-2026-9179

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

The WP Forms Connector plugin for WordPress is vulnerable to SQL Injection via the 'order' parameter of the /wp-json/wp/v3/post/list REST endpoint in versions up to and including 1.8. This is due to insufficient escaping on the user-supplied 'order' parameter (read directly from $_GET['order'] into $shorting) and the lack of sufficient preparation on the existing SQL query in the listPost() function, where the value is concatenated unquoted into the ORDER BY clause and executed via $wpdb->get_results() without $wpdb->prepare(). The endpoint is registered with permission_callback '__return_true' and performs only a broken header-based check that validates the supplied 'Username' corresponds to an administrator account while never verifying the 'Password'. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
29.6%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 25, 2026

References (4)

Vendor Advisories for CVE-2026-9179(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 35× in last 7d / 64× 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-07-07 01:35 UTCEG score recompute
  2. 2026-07-07 01:35 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 13:31 UTCEG score recompute
  5. 2026-07-06 13:31 UTCGHSA enrichment
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 01:22 UTCEG score recompute
  8. 2026-07-06 01:22 UTCGHSA enrichment
  9. 2026-07-05 13:19 UTCEG score recompute
  10. 2026-07-05 13:19 UTCGHSA enrichment
  11. 2026-07-05 02:31 UTCEPSS rescore
  12. 2026-07-05 01:16 UTCEG score recompute
  13. 2026-07-05 01:16 UTCGHSA enrichment
  14. 2026-07-04 12:58 UTCEG score recompute
  15. 2026-07-04 12:57 UTCGHSA enrichment
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 00:54 UTCEG score recompute
  19. 2026-07-04 00:54 UTCGHSA enrichment
  20. 2026-07-03 12:52 UTCEG score recompute
  21. 2026-07-03 12:51 UTCGHSA enrichment
  22. 2026-07-02 23:55 UTCEG score recompute
  23. 2026-07-02 23:55 UTCGHSA enrichment
  24. 2026-07-02 11:53 UTCEG score recompute
  25. 2026-07-02 11:53 UTCGHSA enrichment
Show 39 more
  1. 2026-07-01 23:50 UTCEG score recompute
  2. 2026-07-01 23:50 UTCGHSA enrichment
  3. 2026-07-01 15:07 UTCEPSS rescore
  4. 2026-07-01 11:48 UTCEG score recompute
  5. 2026-07-01 11:47 UTCGHSA enrichment
  6. 2026-06-30 23:45 UTCEG score recompute
  7. 2026-06-30 23:45 UTCGHSA enrichment
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 11:27 UTCEG score recompute
  10. 2026-06-30 11:27 UTCGHSA enrichment
  11. 2026-06-29 23:22 UTCEG score recompute
  12. 2026-06-29 23:22 UTCGHSA enrichment
  13. 2026-06-29 11:20 UTCEG score recompute
  14. 2026-06-29 11:20 UTCGHSA enrichment
  15. 2026-06-28 23:17 UTCEG score recompute
  16. 2026-06-28 23:17 UTCGHSA enrichment
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 11:13 UTCEG score recompute
  19. 2026-06-28 11:13 UTCGHSA enrichment
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-27 23:11 UTCEG score recompute
  22. 2026-06-27 23:11 UTCGHSA enrichment
  23. 2026-06-27 11:08 UTCEG score recompute
  24. 2026-06-27 11:08 UTCGHSA enrichment
  25. 2026-06-27 03:08 UTCEPSS rescore
  26. 2026-06-26 23:04 UTCEG score recompute
  27. 2026-06-26 23:04 UTCGHSA enrichment
  28. 2026-06-26 11:02 UTCEG score recompute
  29. 2026-06-26 11:01 UTCGHSA enrichment
  30. 2026-06-25 19:40 UTCEG score recompute
  31. 2026-06-25 19:40 UTCGHSA enrichment
  32. 2026-06-25 13:50 UTCEPSS rescore
  33. 2026-06-25 07:37 UTCEG score recompute
  34. 2026-06-25 07:37 UTCGHSA enrichment
  35. 2026-06-24 19:35 UTCEG score recompute
  36. 2026-06-24 19:35 UTCGHSA enrichment
  37. 2026-06-24 14:05 UTCEPSS rescore
  38. 2026-06-24 07:32 UTCEG score recompute
  39. 2026-06-24 07:29 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9179?
CVE-2026-9179 is a high vulnerability published on June 24, 2026. The WP Forms Connector plugin for WordPress is vulnerable to SQL Injection via the 'order' parameter of the /wp-json/wp/v3/post/list REST endpoint in versions up to and including 1.8. This is due to insufficient escaping on the user-supplied 'order' parameter (read directly from $GET['order'] into…
When was CVE-2026-9179 disclosed?
CVE-2026-9179 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9179 actively exploited?
CVE-2026-9179 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 29.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9179?
CVE-2026-9179 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-9179?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9179, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-9179?

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

Start Free Scan →Browse All CVEs