Hi gents,

we are also dealing with this issue. Our vulnerability scanner detected this issue first in May 2000, if I remember correctly. 

The deployment of the new version 1.2.6 did not solve this issue. Is there any chance, that the fix will be available by end of November?

Many thanks in advance for your support!

Best regards,

Sascha