gabrielbianconi

I disabled all plugins and activated one by one. I discovered that the error disappears if I disable WP Security Scan.

I have its lastest version, but it seems to generate this bug.