I've already coded a solution into beta 4 to prevent this.
What the next beta version will do is that the ASP session ID is stored in a hidden field in the form, when it is then passed over to the page reading in the details the ASP session ID is requested again and is matched up against that from the form, if they don't match then the user has just enetred the site from another site and a new session ID has started for them so the two won't match. If this happens the user is sent to a page asking them to make sure cookies are enabled on there system and stopping them from registerig. This should stop form inputing from a remote site.
The same has also been added to all pages then send data to the server via a form.
Topic Options
Post Options
Thanks(0)
