Administrative and Maintenance Tools - Fix-it: Template Edition

A common method of defacing vBulletin sites is to edit the parsed template html directly via the database. It makes it harder for administrators to find the issue, and can be a pain in the ass to cleanup if you're not familiar with working with the database.

This tool will make it easier to clean your defaced site.

What it does:
Checks all of the templates in the database:
- Makes a new compiled version from the uncompiled template.
- Compares the current compiled template to the new compiled template
- If they differ, it updates the template, then rebuilds all of the styles.

How do you use it?
- Upload to your admincp, modcp, install, or root forums folder
- Browse to it
- Let it run
- Delete tool_recompiler.php after you are done using it.

This tool now works on vB3 and vB4.

vB4 Thread

[Magle]

Unfortunately it doesn't work under vB 4.1.10, but I really need this a s my forum was compromised. I have since closed the hole (I hope), but the bad templates are still in there I believe

Is there any way to get this to work, and if not, how can I manually reparse the templates?

Any help wold be greatly appreciated, thanks.

[Zachery]

Are you positive its in the templates?

[Brandon Sheley]

Is there a 4.1.x version of this?
I found this thread via theadminzone
http://www.theadminzone.com/forums/s...2&postcount=81
and want to make sure a client is secure.

Thanks

[kh99]

I think for this to work in vb4 you just need to take the "false" parameter off the compile_template line so it looks like this:

    $template['newparsed'] = compile_template($template['template_un']);

[Magle]

Originally Posted by Zachery

Are you positive its in the templates?

I'm not 100% sure, but I believe this may be what happened:

https://www.vbulletin.com/forum/show...=1#post2185387

Both my forums were compromised at the same time, and even after I had plugged the hole this mod continued to send blank emails to me for several days (which according the the author means it found an infection but missed some phrases). It has stopped now though, but does that mean the templates are "clean"?

This may also be what happened (or both), but how to tell? I'd rather be safe than sorry

[Magle]

Originally Posted by kh99

I think for this to work in vb4 you just need to take the "false" parameter off the compile_template line so it looks like this:

    $template['newparsed'] = compile_template($template['template_un']);

Thanks a lot!

I'll try this if/when I can muster the courage to run the untested code on my forums

[kh99]

Originally Posted by Magle

Thanks a lot!

I'll try this if/when I can muster the courage to run the untested code on my forums

That's fair. I did run it on a test forum and it runs without errors, recompiled a template where I had gone in to the db and changed the compiled string, and didn't seem to have any other effects. But personally I don't think I'd even run the original version unless I suspected a problem.

[Magle]

Originally Posted by kh99

That's fair. I did run it on a test forum and it runs without errors, recompiled a template where I had gone in to the db and changed the compiled string, and didn't seem to have any other effects. But personally I don't think I'd even run the original version unless I suspected a problem.

I see, thanks for testing it. I think what I'll do is run it right after the daily backup of my server, that way if something goes wrong It'll be at most a few hours I lose.

[neverstop]

When I try running this file (vb4) I get a blank page. Funny thing is it seemed to work the first time I ran it but got "hung" on a particular template. Now everytime I try to run it i just get a blank page. Any thoughts?

[aVirulence]

I'm getting a 500 error when I try to run this on my vb4 forum (after changing the parameter as discussed above).