Conversation
4 tasks
darylldoyle
approved these changes
Jan 29, 2026
dkotter
approved these changes
Jan 29, 2026
This file contains hidden or 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
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.
Description of the Change
This pull request updates the documentation in both
README.mdandreadme.txtto clarify the security considerations around SVG upload handling in WordPress. The new sections explain why Safe SVG does not globally enable SVG uploads and detail the limitations imposed by WordPress’s upload API, emphasizing the plugin’s focus on security over broad compatibility.Documentation updates regarding SVG upload security:
README.mdandreadme.txt, explaining that WordPress’s_wp_handle_upload()function allows arbitrary actions, making it impossible for Safe SVG to guarantee sanitization across all upload paths. [1] [2]Relates to #286, #296.
How to test the Change
Changelog Entry
Credits
Props @darylldoyle, @jeffpaul.
Checklist: