Skip to content

Security: escape customer/product output in the Broadcast list table#1373

Open
vuckro wants to merge 1 commit into
Ultimate-Multisite:mainfrom
vuckro:security/broadcast-list-table-xss
Open

Security: escape customer/product output in the Broadcast list table#1373
vuckro wants to merge 1 commit into
Ultimate-Multisite:mainfrom
vuckro:security/broadcast-list-table-xss

Conversation

@vuckro

@vuckro vuckro commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Summary

column_target_customers() and column_target_products() interpolated customer
display names, email addresses and product names directly into HTML — including
into single-quoted aria-label attributes. A customer controls their own
display name (WordPress does not HTML-escape display names on save), so a crafted
name is stored and then rendered unescaped when a network admin views the
Broadcasts list — a stored XSS that fires in the network-admin context.

Changes

Escape each interpolated value for its context: esc_url() for links,
esc_attr() for attribute values, esc_html() for text nodes.

Compatibility

Output-only change; rendered markup is identical for non-malicious data.


Part of a small series of focused security hardening PRs. Full technical detail
is available privately to the maintainers on request (coordinated disclosure).

column_target_customers() and column_target_products() interpolated
customer display names, email addresses and product names straight into
HTML — including into single-quoted aria-label attributes. A customer
controls their own display name, so a crafted name (display names are not
HTML-escaped by WordPress on save and may contain quotes) is stored and
then rendered unescaped when a network admin views the Broadcasts list,
yielding stored XSS in the network-admin context.

Escape each interpolated value for its context with esc_url() for links,
esc_attr() for attribute values and esc_html() for text nodes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@vuckro, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 29 minutes and 17 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3bb84336-7024-4f25-8309-21484f997c92

📥 Commits

Reviewing files that changed from the base of the PR and between 1310078 and abb9d40.

📒 Files selected for processing (1)
  • inc/list-tables/class-broadcast-list-table.php
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant