Quick answers
- Is CVE-2026-116609 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116609 being exploited in the wild.
- How severe is CVE-2026-116609?
- Medium severity, with a CVSS score of 6.5, published 28 October 2026.
- Which products and versions are affected?
- WordPress.org WP Visitor Statistics up to 8.8.
- Is there a fix for CVE-2026-116609?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-116609 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-116609?
- Check whether you run WordPress.org WP Visitor Statistics 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
The [wsm_showTrafficStatsList] shortcode accepts user-supplied attributes ('from', 'to', 'first', 'second') that are passed unsanitized into SQL queries executed via wpdb->get_results(). The vulnerable code concatenates these raw attribute values into double-quoted SQL strings in fnGetHourlyReportByDateNameTimeZone() without escaping, allowing SQL injection. Exploitation requires authenticated access with Contributor-level privileges or above, and enables extraction of arbitrary data from the database.
Affected products
- WordPress.org WP Visitor Statistics up to 8.8
Timeline
- 2026-10-28: disclosed