4
Well, number one, until you can identify the exact eploit such as using your access_logs, then you cannot assume that XOOPS is the problem.
You need to look at the access logs around the time your site was hacked.
Also, if you do assume, then assume your server was hacked, not XOOPS.
Once they hack your server, then they can edit stuff like your XOOPS site, but this doesnt mean they got in through XOOPS.
Also, if you are worried about security, then you really need to keep up with the latest version of XOOPS.
At this point, if they did get in through XOOPS, then it would be your fault, for not running the latest stable version (XOOPS 2.0.13a)
Who runs your server? Whats OS is it? Is it shared hosting?
Good Luck,
_Dan
Daniel Hall / XOOPS Module Development & Theme Design
Free XOOPS Support >
My Wish List