Open N-o-Z opened 1 month ago
In case this is not part of the plan: It's cool to do it on the backend, but please (also) protect when inserting the user provided fields into the DOM. So it really needs to be based on an allowlist rather than on a blocklist. That list can come (and probably should) from an existing React library, of course.
@itaigilo I think this is something we can do this current sprint. WDYT?
@itaigilo I think this is something we can do this current sprint. WDYT?
Yeah, I guess so. Will do it on my next workday.
@itaigilo should we close this?
@itaigilo should we close this?
@N-o-Z can we close it?
@itaigilo should we close this?
@N-o-Z can we close it?
There's an open PR linked to this issue - what about it?
There's an open PR linked to this issue - what about it?
It's not relevant anymore - there's no need to sanitize the fields on the UI side, and this PR can be closed.
There's no need because? Also what about the BE?
We should sanitize any user inputted fields in pull requests such as Title and Description to avoid potentially malicious attacks