Skip to content

HTML API: Ensure correct encoding of modified class names #10591

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.

Sign up for GitHub

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

Closed
sirreal wants to merge 4 commits into from
+52 −6
Closed

HTML API: Ensure correct encoding of modified class names #10591

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2c8756b
Add failing test for ticket 64340
sirreal Dec 3, 2025
cf42da8
Include correctly encoded HTML class name "&" initially
sirreal Dec 3, 2025
135f3dd
Add missing attribute decode when accessing raw class attribute HTML
sirreal Dec 3, 2025
99d7043
Update tests enforcing double-encoding
sirreal Dec 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add missing attribute decode when accessing raw class attribute HTML
  • Loading branch information
@sirreal
sirreal committed Dec 3, 2025
commit 135f3dd5b41cda85a43fc48e2ff6ca0d7afc4930
10 changes: 6 additions & 4 deletions src/wp-includes/html-api/class-wp-html-tag-processor.php
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2342,10 +2342,12 @@ private function class_name_updates_to_attributes_updates(): void {
}

if ( false === $existing_class && isset( $this->attributes['class'] ) ) {
$existing_class = substr(
$this->html,
$this->attributes['class']->value_starts_at,
$this->attributes['class']->value_length
$existing_class = WP_HTML_Decoder::decode_attribute(
substr(
$this->html,
$this->attributes['class']->value_starts_at,
$this->attributes['class']->value_length
)
Copy link
Member

@dmsnell dmsnell Dec 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’ve been staring at this for a bit now and have no idea how we missed it. Surely we didn’t overlook this since 6.2 in the original introduction?

but you know what? we did!

php > $p = new WP_HTML_Tag_Processor( '<div class="&amp; &#x61;bc">' );
php > $p->next_tag();
php > $p->add_class( '&' );
php > $p->add_class( 'abc' );
php > echo $p->get_updated_html();
<div class="&amp; &#x61;bc &amp; abc">
php > $p->remove_class( 'abc' );
php > echo $p->get_updated_html();
<div class="&amp; &#x61;bc &amp;">
php > $p->remove_class( '&' );
php > echo $p->get_updated_html();
<div class="&amp; &#x61;bc &amp;">

now I don’t remember why; maybe it was performance-related or maybe it was a choice to lean on already-existing bugs, but I suppose it’s proper here to fix it regardless.

Copy link
Member Author

@sirreal sirreal Dec 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, there's been a latent issue for a while that was covered up by the behavior of esc_html(). It's become very clear with the change in 6.9 to use more rigorous attribute encoding.

);
}

Expand Down