Skip to content
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.

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

Localized text is always trusted content. #428

Open
michaelkrog opened this issue Feb 4, 2025 · 0 comments
Open

Localized text is always trusted content. #428

michaelkrog opened this issue Feb 4, 2025 · 0 comments

Comments

@michaelkrog
Copy link

michaelkrog commented Feb 4, 2025

It seems that text coming in via LocalizationSupport is always considered trusted content and will be output directly and not via fx. OwaspHtmlTemplateOutput.

However, in some contexts, localized text can come from untrusted sources. Maybe an agency was hired to do the translation. Or text are retrieved from a remote system like a CMS. If that is the case and LocalizationSupport is used, XSS exploits seem trivial.

My workaround is to create my own localization that output the localized texts as pure strings for it to become "user content".

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

No branches or pull requests

1 participant