It's not that bad.

Use filter functions and sanity checks for input.

Use htmlspecialchars() basically on output.

That should take care of basically everything.

On Jun 7, 2010, at 6:16 AM, Igor Escobar <> wrote:

This was my fear.

Igor Escobar
Systems Analyst & Interface Designer

+ @igorescobar (twitter)

On Mon, Jun 7, 2010 at 10:05 AM, Peter Lind <> wrote:

On 7 June 2010 14:54, Igor Escobar <> wrote:
Hi Folks!

The portal for which I work is suffering constant attacks that I feel
is PHP Injection. Somehow the hacker is getting to change the cache files that our system generates. Concatenating the HTML file with another that have an iframe to a malicious JAR file. Do you have any suggestions to prevent this action? The hacker has no access to our file system, he is imputing the code through some security hole. The problem is that the
is very big and has lots and lots partners hosted on our estructure
structure. We are failing to identify the focus of this attacks.

Any ideas?

Check all user input + upload: make sure that whatever comes from the
user is validated. Then check all output: make sure that everythin
output is escaped properly. Yes, it's an enormous task, but there's no
way around it.


WWW: /
BeWelcome/Couchsurfing: Fake51

PHP General Mailing List (
To unsubscribe, visit:

Reply via email to