DaDaBIK logo


Security Risk, PLEASE UPGRADE!

Hi all,
last night I discovered an important security hole in DaDaBIK so I decided to immediately release a version 4.3 beta2 with the only purpose of partially fixing it. All the other bug fixes and new features are waiting for the version 4.3 rc1, avaiable in 1 or 2 weeks as expected.

Here is the problem: if in a DaDaBIK application the insert or edit feature was enabled (at least for one table) and a select_single field type was used (at least once, even in another table), a malicious user who had access to the application could in many cases insert in a listbox some arbitrary javascript code, which was then executed by other users just by using the application.
Among other problems, this could lead to XSS attack (, which in turn could allow an unauthorized access to the application ( and, if the Internet browser of the user contained security holes, even the execution of arbitrary code in the client machine.

The new 4.3 beta2 solves this problem. Even the DaDaBIK demo was affected and exploited by a malicious user; now it has been patched.

The problems described above can however occur even when the insert or edit feature was enabled (at least for one table) and the HTML content type is used; at the moment there isn't a patch for this second scenario, so the HTML content type should be used very carefully, as highlighted in the upgraded documentation. In the next few days, I would like to use something like to allow the users to insert html text without security problems.

The 4.3 beta2 also fixes another minor GUI bug, as you can read from the changelog.


  1. JP 12 Nov 2010

    Does this security risk apply to all previous releases of Dababik?

  2. Eugenio 12 Nov 2010

    Yes it does.

  3. JP 12 Nov 2010

    Is there a way to patch older versions without upgrading to 4.3 beta2? Reason I ask is many people like myself use heavily modified versions of Dadabik and I think upgrading would be difficult.

  4. Eugenio 12 Nov 2010

    Yes there is, write me privately.