Wp Buy Visitor Traffic Real Time Statistics vulnerabilities
6 vulnerabilities
Known vulnerabilities in Wp Buy Visitor Traffic Real Time Statistics, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
CVE-2021-24193wordpressvisitors-traffic-real-time-statistics+1
EPSS score1.32%
Low privileged users can use the AJAX action 'cp_plugins_do_button_job_later_callback' in the Visitor Traffic Real Time Statistics WordPress plugin before 2.12, to install any plugin (including a specific version) from the WordPress repository, as well as activate arbitrary plugin from then blog, which helps attackers install vulnerable plugins and could lead to more critical vulnerabilities like RCE.CVE-2021-24829unknownvisitor traffic real time statistics+2EPSS score1.36%
The Visitor Traffic Real Time Statistics WordPress plugin before 3.9 does not validate and escape user input passed to the today_traffic_index AJAX action (available to any authenticated users) before using it in a SQL statement, leading to an SQL injection issueCVE-2019-15832wordpressvisitors-traffic-real-time-statistics+1EPSS score0.80%
The visitors-traffic-real-time-statistics plugin before 1.13 for WordPress has CSRF.CVE-2019-15831wordpressvisitors-traffic-real-time-statistics+1EPSS score0.74%
The visitors-traffic-real-time-statistics plugin before 1.12 for WordPress has CSRF in the settings page.CVE-2026-2936wordpressvisitors-traffic-real-time-statistics+1EPSS score0.32%
The Visitor Traffic Real Time Statistics plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'page_title' parameter in all versions up to, and including, 8.4 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 an admin user accesses the Traffic by Title section.CVE-2026-97341wordpressvisitors-traffic-real-time-statistics+1EPSS score0.27%
The Visitor Traffic Real Time Statistics plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via 'X-Real-IP' HTTP Header in all versions up to, and including, 8.16 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. This requires no authentication, no nonce, and no capability — the wp_ajax_nopriv_ahcfree_track_visitor endpoint accepts the forged X-Real-IP header from any unauthenticated HTTP request and stores the entity-encoded payload verbatim in the database.