http://www.troyhunt.com/2012/06/our-password-hashing-has-no-...
Then note that it was posted two years ago. GPUs surely haven't gotten any slower since then.
At minimum, you need to add unique salt to each password. It forces the attacker to run dictionary on each account separately. It is also recommended to use different slower hash function or iterate MD5/SHA1 thousands times, so he will be much slower.
good: http://en.wikipedia.org/wiki/PBKDF2
gooder: http://en.wikipedia.org/wiki/Scrypt
Maybe avoid using SHA256 with them because of Bitcoin ASICs. If your passwords get leaked in hashed form, even with these, you'll still want to tell your users and advise/force them to change their passwords. Forcing makes more sense if you have 2FA to something not likely to be accessible with their previous password (SMS maybe?)
How so?