Quick answers
- Is CVE-2026-8163 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-8163 being exploited in the wild.
- How severe is CVE-2026-8163?
- Informational severity, with a CVSS score of 7.7, published 23 June 2026.
- Which products and versions are affected?
- Infility Global < 2.15.19.
- Is there a fix for CVE-2026-8163?
- A patch was published on 2026-06-23: Fix released in version 2.15.19 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-8163 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-8163?
- Check whether you run Infility Global at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A SQL injection vulnerability exists in the Infility Global WordPress plugin due to insufficient sanitization and escaping of the 'order' and 'orderby' parameters within the 'control-data' admin page. The plugin appends these parameters directly to SQL queries executed via $wpdb->get_results() without using prepared statements. An authenticated attacker with at least Subscriber-level privileges can exploit this via a crafted GET request to /wp-admin/admin.php. This can be used to perform time-based blind SQL injection or UNION-based attacks to exfiltrate arbitrary data from the WordPress database. The issue is fixed in version 2.15.19.
Affected products
- Infility Global Infility Global < 2.15.19
Timeline
- 2026-06-02: disclosed: Initial public disclosure by WPScan
- 2026-06-23: advisory: NVD publication date
- 2026-06-23: patched: Fix released in version 2.15.19