Use 'ENT_QUOTES|ENT_SUBSTITUTE' for HTML encoding and decoding functions #6583
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.
Discussion on Internals: https://news-web.php.net/php.internals/112782
Changing the HTML encoding/decoding functions to
ENT_QUOTES|ENT_SUBSTITUTE
, because the current default ofENT_COMPAT
is dangerous:This causes a XSS vulnerability because single quote characters are not encoded by default:
This is why all PHP frameworks I can find use
ENT_QUOTES
at a minimum, and will often useENT_SUBSTITUTE
to avoid the whole value being lost due to a single bad character.As to
ENT_HTML401
, I think that still needs to be the default (rather thanENT_HTML5
), as Microsoft Outlook still does not accept'
, and can be an issue with older versions of Android (both are fine with'
).Note: This is the first time I've edited any C code for a project (before now I've only edited things for myself), and while it seems to work, I'd appreciate mistakes can be made (feel free to delete). I'm also happy to attempt changes to the doc-en repo as well.