The vulnerability is caused by the system passing all usernames and passwords to a log file, which can be exploited by sending a 251 char string of /x20 commonly known as a blank space. The vendor has fixed this vulnerability in later releases of its firmware.
A vulnerability exists in Censura v1.16.04, which can be exploited by malicious people to conduct SQL injection and XSS attacks. The vulnerability is caused due to the 'itemid' parameter in 'censura.php' not being properly sanitised before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code. Successful exploitation of the SQL injection vulnerability may allow execution of arbitrary SQL commands. Successful exploitation of the XSS vulnerability may allow execution of arbitrary HTML and script code in a user's browser session in context of an affected site.
A buffer overflow vulnerability exists in Pirch IRC 98 Client (response) due to improper bounds checking of user-supplied input. An attacker can exploit this vulnerability to execute arbitrary code in the context of the application. This vulnerability is being exploited by sending a specially crafted payload to the vulnerable application. This payload contains malicious code that is executed when the application attempts to process the malicious input.
There's no check about the elimination of 'help' directory, then whenever an administrator forget to delete it, we can re-install the CMS, it means we can add a new administrator account, without specify database's informations. The Blind SQL Injection Exploit is a PHP script that can be used to retrieve the password of an administrator account in the d.net CMS. The script uses a socket connection to send a malicious query to the server and then checks the response for the password.
A vulnerability exists in the Joomla component 'com_category' which allows an attacker to inject arbitrary SQL commands. This is done by manipulating the 'edit' parameter in the URL. An attacker can exploit this vulnerability by sending a specially crafted URL to the vulnerable application. The URL contains an SQL query which when executed, will dump the contents of the database. Demos of the exploit can be seen in the URL http://www.hendrygroup.com.au/index.php?option=com_category&task=loadCategory&catid=-9999+AND+1=0+union+all+select%201,2,group_concat(username,0x3a,password),4,5+from+jos_users-- and http://teachandsay.com/index.php?option=com_category&id=12&task=view&color=3&cat_id=-9999+UNION+SELECT+1,2,group_concat(username,0x3a,password),4,5+from+jos_users--.
Multiple SQL Injection vulnerabilities were discovered in Ebay Clone 2009. The first vulnerability is located in the 'feedback.php' file with the 'user_id' parameter. The second vulnerability is located in the 'view_full_size.php' file with the 'item_id' parameter. The third vulnerability is located in the 'classifide_ad.php' file with the 'item_id' parameter. The fourth vulnerability is a Blind SQL Injection located in the 'crosspromoteitems.php' file with the 'item_id' parameter.
This exploit is for Playlistmaker v1.5, which is vulnerable to a stack overflow vulnerability. The exploit creates a malicious .m3u, .m3l, or .txt file which, when opened, causes a stack overflow and crashes the program.
This exploit is a proof of concept for a stack overflow vulnerability in the M3U/M3L to ASX/WPL v1.1 software. The vulnerability is triggered when a maliciously crafted M3U/M3L file is opened, causing a buffer overflow. This can lead to arbitrary code execution.
Morcego CMS is vulnerable to Blind SQL Injection. This exploit allows an attacker to extract the password of a given user from the database. The exploit works by sending a crafted HTTP request to the vulnerable application and analyzing the response. If the response contains the application's title, then the crafted request was successful and the character is extracted from the database.
The vulnerability exists in the 'category.php' and 'search.php' files of the Ebay Clone 2009 script. An attacker can exploit the Blind SQL Injection vulnerability by sending a maliciously crafted HTTP request to the vulnerable script. An attacker can exploit the XSS vulnerability by sending a maliciously crafted HTTP request to the vulnerable script.