In light of vBulletin getting hacked due to hackers gaining the ability to log in as a moderator, we are being proactive and changing our method of storing and checking user passwords. Although we are no longer on the vBulletin platform, and are absolutely not susceptible to being hacked in a similar way, it certainly cannot hurt to take some proactive steps. Up until now, we have been using a somewhat similar method of storing user passwords in the database as vBulletin had, as doing so eased the migration process.

Please bare with me as there might be some intermittent downtime or the inability to log in as we update over one million records on our database this evening.

Edited by Dani: Test deletion

3 Years
Discussion Span
Last Post by Dani

The exploit only applies to vBulletin 4 and 5. PFO is still on vBulletin 3.x.


Password migration complete. Please let me know if you experience any issues.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.