freecrm
New Member
- Messages
- 629
- Reaction score
- 0
- Points
- 0
If you manage to find out the ID of another session, it's very easy to edit your cookie and make the server beleive you are the user which has that specific session assigned. But if you manage to do that, you cannot access the session directly, I mean it's impossible for the user to see the actual session data. That person can only see webpages that were intended for somebody else. So when you make a site, don't just show all info you have on that person. Just require them to enter their password again for each page which has (for example) the ability to change their password, their personal contact information, ...
Let me get this straight.
I have a php login system using the standard Dreamweaver wizard (with an additional variable).
The site I have is a CRM system so there is lots of sensitive data that may be viewable if someone could hack into a session.
If what you are saying is correct, a hacker could potentially see all records that the normal session user could see - aaarrrgghhh!
I don't particularly want a standard user to re-enter his password on every page.
I also use a workgroup id, which is stored as a session variable and only contact records with that workgroup id can be viewed by users with the same workgroup id - is this too at risk?
I'm not very familiar with cookies but I haven't designed the site to use cookies. If you use sessions, does that automatically write cookies in the temp internet files?