MODx Blind SQL Injection

`Product description:  
============  
MODX (originally MODx) is a free, open source content management system and web application framework for publishing content on the world wide web and intranets.  
============  
  
MODX Revolution Blind SQL Injection (CVE-2014-2736)  
============  
The application is vulnerable to blind SQL injection which is exploitable through the session ID supplied by the user. This issue is exploitable without authentication.  
  
Details:  
----------------------  
The vulnerability is triggered where the session ID is inserted into the modx_session table. In this location it is possible to inject SQL sub queries that will be executed by the application.  
  
This issue is exploitable without authentication by passing crafted SQL subqueries into the session ID (PHPSESSID) passed to /index.php. Passing a carefully crafted subquery into the application will cause the application to execute arbitrary SQL queries within the context of database user privileges. Successful injection will cause the application to accept the session and not set a new cookie.  
  
POC is withheld.  
  
Authentication is not required to exploit this issue.  
----------------------  
  
  
MODX Revolution Blind SQL Injection (CVE-2014-2736):  
============  
The messaging and manager functionalities of MODX, are vulnerable to blind SQL injection. Access to these functions requires privileged access.  
  
Details:  
----------------------  
1. The 'user' parameter of /connectors/security/message.php is vulnerable to blind SQL injection.  
2. The 'id' parameter of /manager/index.php is vulnerable to blind SQL injection.  
  
Authentication is required to exploit these vulnerabilities.  
----------------------  
  
The CVE project assigned CVE-2014-2736 to all these issues.  
  
  
Vendor Response:  
Upgrade to MODX 2.2.14 or higher.  
http://modx.com/blog/2014/04/04/revolution-2.2.14/  
  
Timeline:  
============  
March 10, 2014, Vulnerability identified  
March 10, 2014, Product vendor notification  
March 10, 2014, Vendor review  
March 11, 2014, Vulnerability reported  
March 15, 2014, Vulnerability identified  
March 15, 2014, Vulnerability reported  
March 17, 2014, Vendor confirmed issues  
March 20, 2014, Vendor fix confirmed  
April 4, 2014, Patch released  
April 20, 2014, Disclosure  
  
Research:  
============  
Craig Arendt, Stratum Security  
http://www.stratumsecurity.com  
  
Disclaimer:   
The information provided in this advisory is provided as is without warranty of any kind.  
`