>>435311 we all called that this would happen. patch the exploit, make the code work on a modern server, and reset passwords. that's all. bare minimum to get it working and back online.
it's probably setting up the new server that took so long because they had to copy terabytes of active content for one, plus set up all the background processes the code uses.
patching up the SQL wouldn't take much time because you can write a wrapper around that shit (and they already had a semi-working mysqli implementation).
