[pein87]

You can you`ll have to find where the leak is. Its probably someon using some javascript to access the site and them having that info stored by php or perl into a database. My suggestion is to upgrade to a version thats CRSF and XSS protected. I would say 3.7.4 SP1 since the newest 3.6 doenst have the hole fix.

--------------- Added [DATE]1230144309[/DATE] at [TIME]1230144309[/TIME] ---------------

OrgName: RIPE Network Coordination Centre
OrgID: RIPE
Address: P.O. Box 10096
City: Amsterdam
StateProv:
PostalCode: 1001EB
Country: NL

ReferralServer: whois://whois.ripe.net:43

NetRange: 78.0.0.0 - 78.255.255.255
CIDR: 78.0.0.0/8
NetName: 78-RIPE
NetHandle: NET-78-0-0-0-1
Parent:
NetType: Allocated to RIPE NCC
NameServer: NS-PRI.RIPE.NET
NameServer: SEC1.APNIC.NET
NameServer: SEC3.APNIC.NET
NameServer: TINNIE.ARIN.NET
NameServer: SUNIC.SUNET.SE
NameServer: NS.LACNIC.NET
Comment: These addresses have been further assigned to users in
Comment: the RIPE NCC region. Contact information can be found in
Comment: the RIPE database at http://www.ripe.net/whois
RegDate: 2006-08-29
Updated: 2006-09-07

# ARIN WHOIS database, last updated 2008-12-23 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.

there you the ips info

--------------- Added [DATE]1230144367[/DATE] at [TIME]1230144367[/TIME] ---------------

Might be a proxy or shell account it could be hard to know it thats the only IP being used.

--------------- Added [DATE]1230144505[/DATE] at [TIME]1230144505[/TIME] ---------------

Hers a link to more ip info.

http://www.geoiptool.com/en/?IP=78.110.75.21