HomeWordPress vulnerabilitiesWP Visitor Statistics (Real Time Traffic)
WP Visitor Statistics (Real Time Traffic) vulnerabilities
WP Visitor Statistics (Real Time Traffic) has 13 known vulnerabilities in this database. The most recent published record is dated 7 Nov 2026.
- Known vulnerabilities
- 13
- Active installs
- 20,000+
- Latest version
- 8.9.1
- Last updated
- 4 Nov 2026
- Most recent
- 7 Nov 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-111370 | High 7.2 | Up to 8.9.0 | Fixed in a later version (latest 8.9.1) | 7 Nov 2026 |
| Cross-site scripting (XSS) CVE-2026-109230 | High 7.2 | Up to 8.7.1 | Fixed in a later version (latest 8.9.1) | 7 Nov 2026 |
| Cross-site scripting (XSS) CVE-2026-117571 | High 8.8 | Before 8.8 | Fixed in 8.8 | 30 Oct 2026 |
| SQL injection CVE-2026-117572 | Medium 4.1 | Before 8.8 | Fixed in 8.8 | 30 Oct 2026 |
| SQL injection CVE-2026-116609 | Medium 6.5 | Up to 8.8 | Fixed in a later version (latest 8.9.1) | 28 Oct 2026 |
| SQL injection CVE-2026-96267 | High 7.5 | Up to 8.7 | Fixed in a later version (latest 8.9.1) | 3 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-4303 | Medium 6.4 | Up to 8.4 | Fixed in a later version (latest 8.9.1) | 8 Apr 2026 |
| SQL injection CVE-2023-0600 | Critical 9.8 | Before 6.9 | Fixed in 6.9 | 15 May 2023 |
| Cross-site scripting (XSS) CVE-2022-4656 | Medium 5.4 | Before 6.5 | Fixed in 6.5 | 13 Feb 2023 |
| SQL injection CVE-2022-33965 | Critical 9.3 | Before 5.8 | Fixed in 5.8 | 25 Jul 2022 |
| SQL injection CVE-2022-0410 | High 8.8 | Before 5.6 | Fixed in 5.6 | 7 Mar 2022 |
| Cross-site scripting (XSS) CVE-2021-25042 | Medium 5.4 | Before 5.5 | Fixed in 5.5 | 28 Feb 2022 |
| SQL injection CVE-2021-24750 | High 8.8 | Before 4.8 | Fixed in 4.8 | 21 Dec 2021 |
Read the published descriptions
- CVE-2026-111370, 7 Nov 2026
- The WP Visitor Statistics (Real Time Traffic) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'os (also browser, res)' parameter in all versions up to, and including, 8.9.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2026-109230, 7 Nov 2026
- The WP Visitor Statistics (Real Time Traffic) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'browser' parameter in all versions up to, and including, 8.7.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload is stored via an unauthenticated HTTP request to the public visitor tracking endpoint (wmcAction=wmcTrack) and executes when the bundled jqPlot PieRenderer inserts the HTML-decoded series label directly as HTML in the authenticated administrator's browser. CVE record
- CVE-2026-117571, 30 Oct 2026
- The WP Visitor Statistics (Real Time Traffic) WordPress plugin before 8.8 does not sanitize and escape tracking data derived from public visitor requests before storing it and outputting it in the administrative statistics dashboard, allowing unauthenticated attackers to inject arbitrary web scripts that execute when a logged-in administrator views the statistics pages. CVE record
- CVE-2026-117572, 30 Oct 2026
- The WP Visitor Statistics (Real Time Traffic) WordPress plugin before 8.8 does not sanitize and escape a parameter before using it in a SQL statement, allowing high-privilege users such as administrators to perform SQL injection attacks. CVE record
- CVE-2026-116609, 28 Oct 2026
- The WP Visitor Statistics (Real Time Traffic) plugin for WordPress is vulnerable to SQL Injection via the 'from' (and sibling 'to'/'first'/'second') shortcode attribute of the [wsm_showTrafficStatsList] shortcode in versions up to, and including, 8.8 This is due to insufficient escaping on the user-supplied attribute and lack of sufficient preparation on the existing SQL query: `shortcode_atts()` returns attacker-supplied shortcode attributes verbatim (WP core performs no sanitization), only `$atts['id']` is re-sanitized afterward, and the raw value is then concatenated into a double-quoted SQL string literal inside `fnGetHourlyReportByDateNameTimeZone()` (`includes/wsm_db.php:1449`) and executed via `$wpdb->get_results()`. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2026-96267, 3 Oct 2026
- The WP Visitor Statistics (Real Time Traffic) plugin for WordPress is vulnerable to generic SQL Injection via the 'fullRef' parameter in all versions up to, and including, 8.7 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. 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. This is a second-order SQL injection: an unauthenticated attacker submits a crafted referrer URL to the wmcTrack tracking endpoint, which persists the raw unescaped value into the wp_logVisit table, and the injection is triggered when an administrator next views the Traffic Sources dashboard. CVE record
- CVE-2026-4303, 8 Apr 2026
- The WP Visitor Statistics (Real Time Traffic) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'wsm_showDayStatsGraph' shortcode in all versions up to, and including, 8.4 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2023-0600, 15 May 2023
- The WP Visitor Statistics (Real Time Traffic) WordPress plugin before 6.9 does not escape user input which is concatenated to an SQL query, allowing unauthenticated visitors to conduct SQL Injection attacks. CVE record
- CVE-2022-4656, 13 Feb 2023
- The WP Visitor Statistics (Real Time Traffic) WordPress plugin before 6.5 does not validate and escape one of its shortcode attributes, which could allow users with a role as low as contributor to perform Stored Cross-Site Scripting attack. CVE record
- CVE-2022-33965, 25 Jul 2022
- Multiple Unauthenticated SQL Injection (SQLi) vulnerabilities in Osamaesh WP Visitor Statistics plugin <= 5.7 at WordPress. CVE record
- CVE-2022-0410, 7 Mar 2022
- The WP Visitor Statistics (Real Time Traffic) WordPress plugin before 5.6 does not sanitise and escape the id parameter before using it in a SQL statement via the refUrlDetails AJAX action, available to any authenticated user, leading to a SQL injection CVE record
- CVE-2021-25042, 28 Feb 2022
- The WP Visitor Statistics (Real Time Traffic) WordPress plugin before 5.5 does not have authorisation and CSRF checks in the updateIpAddress AJAX action, allowing any authenticated user to call it, or make a logged in user do it via a CSRF attack and add an arbitrary IP address to exclude. Furthermore, due to the lack of validation, sanitisation and escaping, users could set a malicious value and perform Cross-Site Scripting attacks against logged in admin CVE record
- CVE-2021-24750, 21 Dec 2021
- The WP Visitor Statistics (Real Time Traffic) WordPress plugin before 4.8 does not properly sanitise and escape the refUrl in the refDetails AJAX action, available to any authenticated user, which could allow users with a role as low as subscriber to perform SQL injection attacks CVE record
What to do if you run WP Visitor Statistics (Real Time Traffic)
If you run WP Visitor Statistics (Real Time Traffic), open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WP Visitor Statistics (Real Time Traffic) vulnerabilities
Free. We email you when a new vulnerability is published for WP Visitor Statistics (Real Time Traffic), usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.