Just to add to the risk of the hacker brute forcing your password.
Its very unlikely that they will do a bulk brute force de-hashing, - certainly not of all passwords. It would take significant computing resources, - your probably looking at a large scale computing grid being required.
There's no need for the hacker to go to the effort, - there is low hanging fruit to be had.
The biggest danger is if you use a common word for your password.
Eg. Say your password is the word 'password' or 'mypass'. (This is much more common than you think.). This would have a consistent hash value across all passwords in the database with that word.
The hacker could generate the hash for this and other very common passwords that people use, and search the DB for the hashed version.
Bingo, they will have a list of N number of users with the common password words.
The defense to doing the above is password salting. Another word/string is interspersed with your password word, then hashed, to introduce randomness and inconsistency into the hashed value. I'm not sure if the boards DB's password were salted as well as hashed (probably, but not definitely), - its easy enough to reverse password for a significant number of its users if salting isn't used.
However, even salting gives limited protected, - as the salt is usually the persons firstname and/or surname or some other artifact of their personal profile, - so the hacker could still write a script to cycle over the DB and generate the salt, hash for the common passwords and check if yours is one of the more common password words.
So, - to summarize, - if you use a common password word (pretty much any word that can be found in a dictionary), - do change your password for sure.