Opened 8 years ago
Closed 22 months ago
#44637 closed defect (bug) (wontfix)
Escape strings in wp-admin/themes.php
| Reported by: | milana_cap | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Security | Version: | |
| Severity: | normal | Keywords: | has-patch reporter-feedback |
| Cc: | Focuses: | coding-standards |
Description
A lot of translatable strings are not escaped.
Attachments (1)
Change History (5)
#3
@
8 years ago
Hi @SergeyBiryukov,
Thank you for prompt reply. I understand the "trusted" aspect and I apologise for re-opening the discussion.
However, being a developer who often looks into core in order to learn best practice, I find it rather frustrating that examples of good escaping are missing. And this is not something trivial, this is important security matter about which developers have nowhere to learn from. DevHub does explain things in theory and have a few examples but that doesn't cover every situation (like few strings in this file I didn't know how to escape and couldn't find examples anywhere).
If the best practice for WordPress code is not in WordPress core then where should it be?
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Hi @milana_cap, thanks for the ticket!
Could you clarify why these strings should be escaped? Core translations are considered safe because we have a review process for them, see #42639 and the discussion in #30724.
Related: #32233