Proof of concept:
The SQL injection vulnerability exists in the location search action. The "?" character (urlencoded representation: %3f) when included in the lat or lng parameters is converted to the "'contents of the radius parameter'" string that is added to the SQL query. This breaks the legitimate web application's SQL query and allows the user to modify the original query.
Vulnerable / tested versions:
Version 0.2.5 has been tested, furthermore the vendor confirmed that 2.0.0 is affected too.
2012-06-19: Contacting vendor through .
2012-06-19: Vendor reply asking for detailed customer information.
2012-06-20: We won't provide such information, asking for security contact. again, receiving a contact.
2012-06-21: Sending advisory information to security contact and another. contact supplied by vendor support team.
2012-06-22: Vendor is unable to reproduce/exploit the issue
2012-06-22: Describing further steps, asking for affected versions.
2012-06-22: Vendor is able to reproduce SQL error message, asking for more information. v2.0.1 has been released containing "fix for passing the string".
2012-06-25: Sending more exploit details for error-based SQLi.
2012-10-13: Vendor confirms releasing advisory
2012-10-17: SEC Consult releases coordinated security advisory.