Is this not fixed in actually ispconfig version? Code: Possible attack detected. This action has been logged.
This is not a bug, so nothing to be fixed. This message is from the intrusion detection system to point out that a possible harmful POST or GET request was sent to the ISPConfig UI.
You may do that, but I won't do it if I were you. Better check out why it got blocked and what got blocked and then either extend the whitelist to not monitor that specific field or raise the lock score.
I set the score to 50 but in Chrome still the msg is there (in Firefox Developer edition not) Where can i Check why got blocked?
Code: [INTERFACE]: PHP IDS Alert.Total impact: 29<br/> Affected tags: xss, csrf, sqli, id, lfi<br/> <br/> Variable: COOKIE.pmaUser-1 | Value: {"iv":"277FAglp/f/LpNQakZIQJA==","mac":"449aad86e6c56b987b2c83265bfe40155402fea4","payload":"9N9QX4twyNOlSuQdOojFZg=="}<br/> Impact: 29 | Tags: xss, csrf, sqli, id, lfi<br/> Description: Finds attribute breaking injections including whitespace attacks | Tags: xss, csrf | ID 2<br/> Description: Detects classic SQL injection probings 2/2 | Tags: sqli, id, lfi | ID 43<br/> Description: Detects basic SQL authentication bypass attempts 2/3 | Tags: sqli, id, lfi | ID 45<br/> Description: Detects basic SQL authentication bypass attempts 3/3 | Tags: sqli, id, lfi | ID 46<br/> Description: Detects MySQL comment-/space-obfuscated injections and backtick termination | Tags: sqli, id | ID 57<br/> <br/>
