Validate/escape db fields to avoid XSS attack

[batopa]

To avoid XSS attack we need validating and/or escaping untrusted fields to/from database.

More details here (thanks to Steffen Rösemann)

Registered users, who are allowed to use the administrative backend (as translator or editor for example) are able to use arbitrary HTML and/or JavaScript-code which gets stored in the database backend without being sanitized. This has an effect on other registered users on the administrative backend, as the code is executed when visiting the sites prepared by an attacker.
The vulnerabilities are found in the following URLs on a normal BEdita installation:

http://{TARGET}/index.php/home/profile (in form with id „editProfile“ via input field with id „lrealname")
http://{TARGET}/index.php/ (inform with id „addQuickItem“ via input field with name "data[title]" and name "data[description]")
http://{TARGET}/index.php/areas (in form with id „saveNote“ via input field with id „notetext")
http://{TARGET}/index.php/documents/view (in form with id „updateForm“ via input field with id „titleBEObject“ and input field with id „tagsArea“)

If you, for example, write a simple <script>alert(document.cookie)</script> in the above mentioned input fields and save it, it will get executed, when visiting the prepared site. That can be a security issue, if for example a translator-user with not as much administrative rights as the administrator is abusing the vulnerabilities and tricks the administrator to visit the sites.
I found out, that injecting code in the input field with id „tagsArea“ gets as well executed on the frontend, when guest users are visiting the page.

[ghost]

This issue has been assigned CVE-ID CVE-2015-1040. See http://seclists.org/oss-sec/2015/q1/115. Greetings!

[batopa]

The issues reported and many others are fixed on 3-corylus branch. The patch will be soon available in the next release.

[stefanorosanelli]

did some testing, everything seems ok now
closing