25
Yesterday, it was posted in the forum that the site of SourceForge.JP had been cracked.
http://sourceforge.jp/forum/forum.php?forum_id=4153 (Japanese)
There was no report to XOOPS japan team before this notice.
And it was making abruptly public for the user.
When this notice was received and the investigation began,
the security hole remained in the corrected one the other (Reported to the vender),
and there must be a possibility that contents have already been falsified by using this hole (1.2.1 former).
Therefore, the post to the XOOPS community had been performed
before information finished being settled.
Being possible to say now,
1. Isolate a pertinent module from web browsers more temporarily than accessible places.
2. Confirm whether there are signs that the cracking was tried to the access log.
3. If signs are discovered, you must confirm whether contents are falsified at once.
(In this case, you must examine the interruption of temporary service.)
4. If it can be confirmed not to be falsified, the service is restarted with a pertinent module isolated.
5. Please wait for the continued information.