Jump to content

PHP hacking and defacing


LanceT

Recommended Posts

Well a lot of those get hacked because their source code is freely available so if there is a page that is vulnerable to cross site scripting or sql injection its easier to find. Then, once a vulnerability is found, its easy to search for other sites using that software and hack them.

 

So those are two strikes you won't have against you. But to answer your question, don't trust anything that comes from the user (cookies, get, post, etc)

Well a lot of those get hacked because their source code is freely available so if there is a page that is vulnerable to cross site scripting or sql injection its easier to find. Then, once a vulnerability is found, its easy to search for other sites using that software and hack them.

 

So those are two strikes you won't have against you. But to answer your question, don't trust anything that comes from the user (cookies, get, post, etc)

 

alright that's good to hear. What I am currently doing to check if the passwords match is first check if the set cookie's username matches the database username as well as the set cookie's password matches the database's password before allowing a user to have any access to confidential pages.

 

Is this a good way to prevent hacking?

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.