Make WordPress Core

Opened 10 years ago

Last modified 5 years ago

#30036 new defect (bug)

Add some escaping to $handle when printing styles.

Reported by: georgestephanis's profile georgestephanis Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Script Loader Keywords: needs-patch
Focuses: Cc:


There's a number of instances where we're currently printing out the dependency handle without any sort of escaping. We should probably do something about that.


Things can currently get somewhat mucked up if someone enqueues a script or style with a single quote in it, that breaks out of the id attribute.

I'm not sure what the best fix for this is, attached are some starting point unit tests to demonstrate the varied types of handles that work currently, that we'll want to at least take into consideration.

Attachments (1)

unit-test.test_awkward_handles_are_supported_consistently.diff (1.6 KB) - added by georgestephanis 10 years ago.

Download all attachments as: .zip

Change History (4)

#1 @azaozz
10 years ago

Thinking we should be more restrictive. Don't see a good reason to support anything except [a-zA-Z0-9_-]+ for handles, both JS and CSS. To stay back-compat we can filter the handles on adding and using them, i.e. replace "unwanted" chars with dashes and throw "Doing it wrong".

#2 @georgestephanis
10 years ago

I'd be most comfortable if we used esc_attr() right before the output. That has the least chance for breakage on backward compatibility if someone's trying to call wp_style_add_data() on a funkily-named asset that had previously worked -- and now suddenly doesn't.

If we were building the system from scratch and didn't have to worry about backward compatibility, I'd probably also add one on when the dependency is registered/enqueued, but still as we do tend to work off of globals, would probably want the added security of esc_attr()'ing the output.

#3 @chriscct7
8 years ago

  • Keywords needs-patch added
Note: See TracTickets for help on using tickets.