229 matches found
WordPress WP Statistics Plugin <= 8.3 - Stored & Reflected XSS
This plugin is prone to stored and reflected cross site scripting vulnerabilities. Solution Update the plugin...
WordPress WP Statistics Plugin <= 9.1.2 - Stored Cross Site Scripting
This plugin is prone to a cross site scripting vulnerability because "above" parameter is vulnerable to cross site scripting. A malicious administration can hijack other users session, take control of another administrator's browser or install malware on their computer. Solution Update the plugin...
Wordpress WP Statistics persistent cross site scripting
=========================================================== Stored XSS Vulnerability in WP Statistics Wordpress Plugin =========================================================== . contents:: Table Of Content Overview ======== Title :Stored XSS Vulnerability in WP Statistics Wordpress Plugin...
WordPress WP Statistics 9.1.2 Cross Site Scripting
=========================================================== Stored XSS Vulnerability in WP Statistics Wordpress Plugin =========================================================== . contents:: Table Of Content Overview ======== Title :Stored XSS Vulnerability in WP Statistics Wordpress Plugin...
WP Statistics <= 9.1.2 - Authenticated Stored Cross-Site Scripting (XSS)
The WP Statistics WordPress plugin was affected by an Authenticated Stored Cross-Site Scripting XSS security vulnerability...
WP Statistics <= 8.4 - Unauthenticated Referer Header Stored XSS
On the "Statistics Visitors" screen the referer link is not filtered. Malicious JavaScript can be injected by an unauthenticated user. This simple cURL command with a custom referer header makes it possible: curl -H 'Referer: javascript:alertlocation.href;' 'http://wp.dev'...
WordPress 4.0.1 Cross-Site Scripting Vulnerability Patch
WordPress’s latest update, 4.0.1, patches a critical cross-site scripting vulnerability affecting comment boxes on websites running the content management system software. An attacker would need only to inject malicious JavaScript into a comment that would infect a reader viewing it on the webpag...