# CVE-2026-116609: WordPress WP Visitor Statistics SQL injection in shortcode

Source: https://junglewise.ai/threats/cve-2026-116609-the-wp-visitor-statistics-real-time-traffic-plugin-for-wordpress  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-28. Updated: 2026-10-28  
License: CC BY 4.0 with a link back

CVE-2026-116609 · Severity: medium · CVSS 6.5 · Published 2026-10-28

The WP Visitor Statistics plugin for WordPress contains a SQL injection vulnerability in a shortcode used to display traffic statistics reports. An authenticated attacker with Contributor-level access can manipulate shortcode parameters to inject malicious SQL commands and extract sensitive data from the WordPress database without proper authorization.

Vendors: [WordPress.org](https://junglewise.ai/threats/vendors/wordpress-org).

## 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

## References

- [https://plugins.trac.wordpress.org/browser/wp-stats-manager/tags/8.8/includes/wsm_db.php](https://plugins.trac.wordpress.org/browser/wp-stats-manager/tags/8.8/includes/wsm_db.php)
- [https://plugins.trac.wordpress.org/browser/wp-stats-manager/tags/8.8/includes/wsm_db.php](https://plugins.trac.wordpress.org/browser/wp-stats-manager/tags/8.8/includes/wsm_db.php)