Fix json encode potential XSS when in script tags - #13050
Merged
Conversation
cdrini
force-pushed
the
fix/json-encode-escape
branch
from
June 26, 2026 15:21
b855291 to
38362a4
Compare
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
cdrini
force-pushed
the
fix/json-encode-escape
branch
from
June 26, 2026 15:39
38362a4 to
c5d3b47
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We often use
<script>$:json_encode(...)</script>, but this is susceptible to XSS if the the object being JSON-stringified contains closing script tags, egBecomes:
Here we also replace
</>with\u003cand\u003eto prevent it being interpreted as a closing script tag:Technical
DRY'd up our two implementation of json_encode so the fix would only need to happen in one spot.
Testing
Also tested by adding the above html sample to the status page locally, and confirmed it no longer XSS's.
Confirmed reading log stats, where we use this pattern, renders correctly.
Screenshot
Stakeholders