original_string: public static function validPathStr($theFile) {
  		if (strpos($theFile, '//') === FALSE && strpos($theFile, '\\') === FALSE && !preg_match('#(?:^\.\.|/\.\./|[[:cntrl:]])#u', $theFile)) {
  			return TRUE;
  		}
  
  		return FALSE;
  	}
code: public static function validPathStr($theFile) {
  		if (strpos($theFile, '//') === FALSE && strpos($theFile, '\\') === FALSE && !preg_match('#(?:^\.\.|/\.\./|[[:cntrl:]])#u', $theFile)) {
  			return TRUE;
  		}
  
  		return FALSE;
  	}
code_tokens: public static function validPathStr ( $ theFile ) { if ( strpos ( $ theFile , '//' ) === FALSE && strpos ( $ theFile , '\\' ) === FALSE && ! preg_match ( '#(?:^\.\.|/\.\./|[[:cntrl:]])#u' , $ theFile ) ) { return TRUE ; } return FALSE ; }
docstring: Checks for malicious file paths.
  
  Returns TRUE if no '//', '..', '\' or control characters are found in the $theFile.
  This should make sure that the path is not pointing 'backwards' and further doesn't contain double/back slashes.
  So it's compatible with the UNIX style path strings valid for TYPO3 internally.
  
  @param string $theFile File path to evaluate
  @return boolean TRUE, $theFile is allowed path string, FALSE otherwise
  @see http://php.net/manual/en/security.filesystem.nullbytes.php
  @todo Possible improvement: Should it rawurldecode the string first to check if any of these characters is encoded?
docstring_tokens: Checks for malicious file paths .