Secure user data #15
Merged
Secure user data #15
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The current version allows saving unsafe data, like HTML containing a `<script>` tag. This patch will apply the `pre_user_description` and `pre_user_display_name` filter, which include the `sanitize_text_field` and `wp_filter_kses` function calls, that would strip insecure HTML data, while still allowing HTML like images, links and similar.
2ndkauboy
force-pushed
the
fix/secure-user-data
branch
from
79b372b to
801fca1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current version allows saving unsafe data, like HTML containing a
<script>tag.This patch will apply the
pre_user_descriptionandpre_user_display_namefilter, which include thesanitize_text_fieldandwp_filter_ksesfunction calls, that would strip insecure HTML data, while still allowing HTML like images, links and similar.