Actions
Bug #16920
openPotential stored XSS in ``status_monitoring.php`` via saved views
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:
Description
When saving views on status_monitoring.php none of the fields have validation, and some can be printed back to the user without encoding in certain circumstances, leading to a potential stored XSS.
Furthermore there is a lot of room for improvement/cleanup in the code around these options, and in general. At a minimum it needs validation and to check/correct the encoding when outputting category.
Files
Actions
Also available in: Atom