metallicrazy

Yeh I am going to need to review what limitations I want to put on inputs. I do appreciate the feedback, it is giving me a lot to think about. Il allow the underscore but need to ensure I'm restricting all common dangerous functions that contain them. It is important that I find a solution to the concat work around though as that is a major loophole. If I were to cut back on restrictions, what would the main ones that should stay be?

Is there a solution?Perhaps removing quotes, dots and white space before running the check?

Thank you for the response. I have compiled a comprehensive list of functions that I could think of, some of which may need to be removed but figured I'd plug the hole and then only open passages where necessary. The function is to test the user input from a text area inside a web app for the banned words.Your are correct, the application is intended to demonstrate the basic functionality of php and not advanced functionality. I have never been taught during my time at uni how to modify a php.ini file. Can you link me to a tutorial?

I am trying to create a comprehensive php e-learning environment for my honours project that will have a "try it yourself" editor. (limited of course). If you want to help me build the security and be part of my testing focus group, please see my forum page. http://w3schools.inv...l=&fromsearch=1

I am currently creating an e-learning application for my honours project (This will not go live or be distributed for profit) that teaches php to brand new users however there will obviously be experienced users using the application as well and they will try to attack it or bring it down. My code to process the user input for malicious code strings before it is run thru an eval(); is below.If any of the banned words are found it returns false and the user input never gets near an eval() function. If no banned words are found then it returns true and the input (PHP CODE) is run thru an eval();