Skip to content

[bot] Merge 25.7 to 25.11#1169

Open
github-actions[bot] wants to merge 2 commits into
release25.11-SNAPSHOTfrom
25.11_fb_bot_merge_25.7
Open

[bot] Merge 25.7 to 25.11#1169
github-actions[bot] wants to merge 2 commits into
release25.11-SNAPSHOTfrom
25.11_fb_bot_merge_25.7

Conversation

@github-actions

Copy link
Copy Markdown

Generated automatically.
Merging changes from: 21d8347
Approve all matching PRs simultaneously.
Approval will trigger automatic merge.
Verify all PRs before approving: https://internal.labkey.com/Scrumtime/Backlog/harvest-gitOpenPullRequests.view?branch=25.11_fb_bot_merge_25.7

labkey-martyp and others added 2 commits July 22, 2026 11:18
## Rationale

BillingNotification.createChargeSummaryReport built its
per-financial-analyst tables by concatenating editor-entered database
values (investigator, project, debitedAccount, projectNumber, category)
and their derived URLs directly into HTML with no escaping. That HTML is
rendered verbatim into the LDK RunNotificationAction admin preview via
HtmlString.unsafe and is also sent as the HTML email body, so a stored
payload in any of those project/alias fields executed in the browser of
any user who previewed the notification or received the email — a stored
XSS with privilege-escalation potential toward admins. The adjacent
Charge Summary category table already escaped its values with
PageFlowUtil.filter; this loop was simply never given the same
treatment.

## Related Pull Requests

None.

## Changes

- Wrap every editor-entered value (investigator, project, account,
project number, category) in PageFlowUtil.filter before rendering it
into the charge summary tables.
- Filter the derived href URLs (project, account, and
per-field-descriptor links), which embed those same tainted values.
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.

2 participants