Potential fix for code scanning alert no. 23: DOM text reinterpreted as HTML #3826
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.
Potential fix for https://github.com/thorsten/phpMyFAQ/security/code-scanning/23
In general, to fix DOM text reinterpreted as HTML, avoid assigning untrusted or non-HTML content to
innerHTML. Instead, assign it totextContent/innerTextor use DOM APIs to build elements, so the browser treats it strictly as text and not as markup.Here, we never intend
outputto contain HTML—it's just a human-readable file size string. The best fix is:fileSize.innerHTML = output;withfileSize.textContent = output;, so the value is inserted as plain text.fileSize.innerHTML = '';withfileSize.textContent = '';. This keeps the pattern consistent and removes unnecessary use ofinnerHTML.These changes are localized to
phpmyfaq/admin/assets/src/content/attachment-upload.ts:textContent.textContent.No extra imports, methods, or definitions are needed;
textContentis a standard property ofHTMLElement.Suggested fixes powered by Copilot Autofix. Review carefully before merging.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.