A SQL injection vulnerability exists in Joomla! Component OS Property v3.0.8. An attacker can exploit this vulnerability by sending a malicious SQL query to the vulnerable parameter 'catIds[0]'. This can allow the attacker to gain access to sensitive information from the database.
A SQL injection vulnerability exists in Joomla! Component JomWALL v4.0, which allows an attacker to inject malicious SQL queries via the 'wuid' parameter in the 'gethovercard' task of the 'com_awdwall' component. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code in the 'wuid' parameter value.
A SQL injection vulnerability exists in Joomla! Component Joomloc-Lite v1.3.2. An attacker can send a specially crafted HTTP request to the vulnerable application in order to execute arbitrary SQL commands in the back-end database. This can potentially result in the manipulation or disclosure of application data.
A SQL injection vulnerability exists in Joomla! Component Joomloc-CAT v4.1.3. An attacker can exploit this vulnerability by sending a specially crafted HTTP request to the vulnerable application. This can allow the attacker to execute arbitrary SQL commands on the underlying database.
A SQL injection vulnerability exists in Joomla! Component WMT Content Timeline v1.0, which allows an attacker to execute arbitrary SQL commands via the 'id' parameter in the 'returnArticle' task. An attacker can use this vulnerability to gain access to sensitive information stored in the database.
A SQL injection vulnerability exists in Joomla! Component Groovy Gallery v1.0.0. An attacker can send a specially crafted HTTP request containing malicious SQL statements to the vulnerable application in order to gain access to unauthorized information or to manipulate data. The vulnerable parameters are 'filter_category' and 'groovy_category' which can be found in the URL.
A SQL injection vulnerability exists in Joomla! Component Team Display v1.2.1. An attacker can exploit this vulnerability by sending a malicious SQL query to the vulnerable parameter 'filter_category' in the 'index.php' script. This can allow the attacker to gain access to sensitive information from the database.
A SQL injection vulnerability exists in Joomla! Component JEmbedAll v1.4. An attacker can exploit this vulnerability by sending malicious SQL queries to the vulnerable application. This can allow the attacker to gain access to sensitive information stored in the database, such as user credentials, or to modify the data stored in the database.
dotCMS versions up to 3.6.1 (and possibly others) are vulnerable to blind boolean SQL injection in the q and inode parameters at the /categoriesServlet path. This servlet is a remotely accessible, unauthenticated function of default dotCMS installations and can be exploited to exfiltrate sensitive information from databases accessible to the DMBS user configured with the product. Exploitation of the vulnerability is limited to the MySQL DMBS in 3.5 - 3.6.1 as SQL escaping controls were added to address a similar vulnerability discovered in previous versions of the product. The means of bypassing these features which realise this vulnerability have only been successfully tested with MySQL 5.5, 5.6 and 5.7 and it is believed other DMBSes are not affected. Versions prior to 3.6 do not have these controls and can be exploited directly on a greater number of paired DMBSes. PostgreSQL is vulnerable in all described versions of dotCMS when PostgreSQL standard_confirming_strings setting is disabled (enabled by default). The vulnerability is the result of string interpolation and directly SQL statement execution without sanitising user input.
Ad name input fields aren't properly escaped. This could lead to an XSS attack that could possibly affect administrators,users,editor. To exploit, go to http://localhost/wp-admin/options-general.php?page=corner-ad.php, click on create new Add button, and use Ad name as "/><svg/onload=prompt(document.domain)>. Fill the other field and click on save corner Add button. If a normal editor,author visit the corner add list page, the XSS will effect them also.
Services By CQR