Is CVE-2026-96267 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-96267 being exploited in the wild.

How severe is CVE-2026-96267?

High severity, with a CVSS score of 7.5, published 3 October 2026.

Which products and versions are affected?

WP Visitor Statistics (Real Time Traffic) up to and including 8.7.

Is there a fix for CVE-2026-96267?

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-96267 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-96267?

Check whether you run WP Visitor Statistics (Real Time Traffic) 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.

CVE-2026-96267: WP Visitor Statistics plugin SQL injection via fullRef parameter

CVE-2026-96267 · Severity: high · CVSS 7.5 · Published 2026-10-03

The WP Visitor Statistics (Real Time Traffic) plugin for WordPress, which tracks website visitor analytics, is vulnerable to SQL injection attacks. An unauthenticated attacker can craft a malicious referrer URL that, when processed, allows them to extract sensitive information from the website's database when an administrator views the Traffic Sources dashboard. This could expose customer data, credentials, or other confidential information stored in the database.

Technologies: WP Visitor Statistics (Real Time Traffic). Vendors: WP Visitor Statistics.

Quick answers

Is CVE-2026-96267 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-96267 being exploited in the wild.
How severe is CVE-2026-96267?: High severity, with a CVSS score of 7.5, published 3 October 2026.
Which products and versions are affected?: WP Visitor Statistics (Real Time Traffic) up to and including 8.7.
Is there a fix for CVE-2026-96267?: 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-96267 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-96267?: Check whether you run WP Visitor Statistics (Real Time Traffic) 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 vulnerability is a second-order SQL injection in the 'fullRef' parameter of the wmcTrack tracking endpoint, caused by insufficient input escaping and lack of prepared statements. An unauthenticated attacker submits a crafted referrer URL that persists unescaped into the wp_logVisit table; the injection is triggered when an administrator views the Traffic Sources dashboard, allowing SQL query manipulation and unauthorized data extraction.

Affected products

WP Visitor Statistics WP Visitor Statistics (Real Time Traffic) up to and including 8.7

Timeline

2026-10-03: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.