Derek – That’s all I was thinking was that it might be being targeted, if there’s some loose code somewhere. I’m not at home right now, but I’ll email you when I get back with more. What happens is that the index.php of this and only this plug-in gets over-written or corrupted with a bunch of other stuff, which, of course, causes WP to disable it. I -think- that might open up other parts of the theme that relay on OT for functionality.
The only fix I’ve done so far is to look for other corrupted files, and replace OT with a fresh copy. Everything works fine until they replace the index.php file again.
As far as I know timthumb isn’t on the site at all, and isn’t in the current theme (no pages use the usual “TimThumb” custom field. I’ll look closer when I get home.
The client may have added a theme – not in use – that uses it, also. Would that be a vulnerability, or only the theme in use? I’ll look and see if there are any inactive themes they added and I haven’t deleted yet.
Thanks for all the action on this, by the way. I’m sorry for the initial confusion that caused a momentary unavailability.