dhtmlxConnector is open to external access of other programs and any external user is allowed to change data in database.

Thus, adding some kind of session-based authentication is strongly recommended.

Basic security

The built-in security manager allows you to limit connector to certain operations.

$gridConn->access->deny("read"); //blocks Select action
$gridConn->access->deny("insert"); //blocks Insert action
$gridConn->access->deny("update"); //blocks Update action
$gridConn->access->deny("delete"); //blocks Delete action

By default, the connector allows all operations.

Protection from cross-site scripting (XSS)

Starting from version 1.5, dhtmlxConnector allows you to protect an app from XSS attacks.

To avoid XSS attacks, the library checks all data inputted by users and according to the set security level doesn't allow HTML or JS code to be inserted.

3 security levels are available:

  • DHX_SECURITY_SAFETEXT (default) - all HTML data is removed from the input field;
  • DHX_SECURITY_SAFEHTML - allows HTML data, but removes possible script tags and handlers;
  • DHX_SECURITY_TRUSTED - input fields are not filtered at all (similar to the previous version of connectors).

To set the necessary security level, use the next code:

ConnectorSecurity::$xss = DHX_SECURITY_SAFETEXT;
//ConnectorSecurity::$xss = DHX_SECURITY_SAFEHTML;
//ConnectorSecurity::$xss = DHX_SECURITY_TRUSTED;

If you want to enable the same behavior as the previous versions of connectors had, set the DHX_SECURITY_TRUSTED mode.

Preventing CSRF and XSRF attacks

The functionality requires 3.5 or later version of the DHTMLX Suite package

The protection is available starting from version 1.5 and can be activated by the following code line:

ConnectorSecurity::$security_key = true;

After calling such a command, connectors start to include additional security keys to all data loading operations and process data updating calls only if they contain the same keys. As a result of this processing, it's impossible to trigger a data updating operation from some third-party site, even if an attacker has access to the valid user session.

The technique is based on php sessions and it's assumed that any php session will be preserved between separate script calls (default php behavior).

Please make sure that you understand what CSRF attack is, as the stated technique won't prevent access to the connector from external urls, it will only prevent execution actions through someone else's session.

Back to top