# Is Kirby secure?

**URL:** <https://forum.getkirby.com/t/is-kirby-secure/1806>\
**Category:** Questions\
**Tags:** v2\
**Created:** [August 11, 2015, 12:30pm UTC](https://forum.getkirby.com/t/is-kirby-secure/1806 "2015-08-11T12:30:15Z")\
**Posts on this page:** 1\
**Showing post:** 38

<div class="post-metadata">

**Author:** ![marianoviola](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/marianoviola/32/3161_2.png) [@marianoviola](https://forum.getkirby.com/u/marianoviola)\
**Post date:** [November 11, 2015, 8:47am UTC](https://forum.getkirby.com/t/is-kirby-secure/1806/38 "2015-11-11T08:47:31Z")

</div>

> [@bastianallgeier](#):
>
> Something I can’t really controll is the code quality of plugins and of templates. Especially unfiltered and unsanitized input can do a lot of harm to any system. Kirby is no exception here. I can maybe only give more hints how to write secure frontend forms and stuff like that and how to use Kirby’s toolkit and other tools to filter input.

Probably I asked about CSRF protection in the [wrong place](https://forum.getkirby.com/t/kirby-2-2-public-beta/2272/23) but then I found an answer by myself.

The toolkit provides a `csrf()` helper but unfortunately it is still undocumented. I think that using CSRF protection is one of the basic tools, along with input [validation and sanitization](http://getkirby.com/docs/security#input-filtering-and-sanitization), that helps to create secure themes and plugins.

---

_[View the full topic](https://forum.getkirby.com/t/is-kirby-secure/1806)._