14 matches found
EUVD-2016-1976
Malware in sbrugna...
EUVD-2016-1975
Malware in sbrugna...
CVE-2016-10985
The echosign plugin before 1.2 for WordPress has XSS via the templates/addtemplates.php id parameter...
CVE-2016-10984
The echosign plugin before 1.2 for WordPress has XSS via the inc.php page parameter...
CVE-2016-10984
The echosign plugin before 1.2 for WordPress has XSS via the inc.php page parameter...
CVE-2016-10985
The echosign plugin before 1.2 for WordPress has XSS via the templates/addtemplates.php id parameter...
CVE-2016-10985
The echosign plugin before 1.2 for WordPress has XSS via the templates/addtemplates.php id parameter...
Design/Logic Flaw
The echosign plugin before 1.2 for WordPress has XSS via the inc.php page parameter...
CVE-2016-10985
The echosign plugin before 1.2 for WordPress has XSS via the templates/addtemplates.php id parameter...
CVE-2016-10984
The echosign plugin before 1.2 for WordPress has XSS via the inc.php page parameter...
PT-2019-7777
Name of the Vulnerable Software and Affected Versions echosign plugin for WordPress versions prior to 1.2 Description The issue concerns a problem with the echosign plugin, where there is a possibility of XSS Cross-Site Scripting attack. This attack can occur via the "page" parameter in the inc.p...
PT-2019-7778
Name of the Vulnerable Software and Affected Versions echosign plugin for WordPress versions prior to 1.2 Description The issue allows for XSS via the id parameter in the "templates/add templates.php" endpoint. Recommendations For versions prior to 1.2, update to version 1.2 or later to resolve t...
WordPress Echosign 1.1 Cross Site Scripting
FULL DISCLOSURE Product : Echosign Plugin Exploit Author : Rahul Pratap Singh Version :1.1 Home page Link : https://wordpress.org/plugins/echosign/ Website : 0x62626262.wordpress.com Linkedin : https://in.linkedin.com/in/rahulpratapsingh94 Date : 21/4/2016 XSS Vulnerability:...
WordPress Echosign Plugin <= 1.1 - Reflected Cross Site Scripting
This plugin is prone to a reflected cross site scripting vulnerability, because "page" and "id" parameters are not sanitized. Solution There is no fix available...