A blind SQL injection vulnerability exists in Xbtit 3.1 via the sid parameter in ajaxchat/getHistoryChatData.php file that is accessible by a registered user. As a result, a malicious user can extract sensitive data such as usernames and passwords and in some cases use this vulnerability in order to get a remote code execution on the remote web server.
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Link | Tags |
---|---|
https://github.com/btiteam/xbtit-3.1/blob/master/ajaxchat/getHistoryChatData.php | third party advisory exploit |
https://emaragkos.gr/infosec-adventures/xbtit-3-1-sql-njection/ | third party advisory exploit |
https://github.com/btiteam/xbtit-3.1/issues/6 | third party advisory exploit |