Audit all calls to mark_safe()
to ensure any user-provided data is escaped
#16700
Labels
status: accepted
This issue has been accepted for implementation
type: housekeeping
Changes to the application which do not directly impact the end user
Proposed Changes
There are many places we use Django's
mark_safe()
utility to bypass HTML escaping (typically within template tags and filters). Any user-sourced data within the string being marked as safe must be manually passed throughescape()
.Justification
Ensures consistent sanitization of user input.
The text was updated successfully, but these errors were encountered: