-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: solve vulnerability with script metadata #816 #817
fix: solve vulnerability with script metadata #816 #817
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only one issue with the function return comment. Otherwise a strong PR 💪
@Soare-Robert-Daniel I think this could have been an NIT so as to not block instead of a change request. |
@preda-bogdan, I was thinking about that. But I considered it pretty important since analyzing tools use the PHPDocs heavily. I see that PHPStan is not enabled in this project, which normally should not pass the check. I considered this NIT as an exception. |
@preda-bogdan Tested and the issue is fixed now, thank you 👍 |
🎉 This PR is included in version 2.10.27 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Summary
Fixes a vulnerability with using the custom fields to save data to the header/footer script boxes when the user does not have the capability to save
unfiltered_html
.Screenshots
Post Preferences (pic. 1)
Post Preferences (pic. 2)
New custom fields name options (pic. 3)
How to test
Contributor
roleContributor
obfx-header-scripts
andobfx-footer-scripts
is not listed under the Add new custom field name.References: Codeinwp/themeisle#1612
Closes: #816