Critical · published June 23, 2023
🚨 A sneaky stored XSS vulnerability puts users at risk just by visiting a page! 🔥 Think of your wiki like a restaurant where any chef (user with edit rights) can add a new dish (payload) to the menu (page title). If the kitchen staff (other users) don’t check the recipe before serving, they might end up tasting something absolutely toxic! This flaw could allow an attacker to inject malicious scripts, leading to stolen credentials, unauthorized actions, and a complete compromise of user accounts. If left unpatched, it’s like leaving the doors wide open for troublemakers to wreak havoc on your wiki!
Think of your wiki like a restaurant where any chef (user with edit rights) can add a new dish (payload) to the menu (page title). If the kitchen staff (other users) don’t check the recipe before serving, they might end up tasting something absolutely toxic! In XWiki versions 5.4.4 up to 14.4.7, 14.10.3, and 15.0, users with edit rights can exploit a stored XSS vulnerability by adding a class with a malicious payload in the title. When other users visit the affected page, the script executes in their browsers.
This flaw could allow an attacker to inject malicious scripts, leading to stolen credentials, unauthorized actions, and a complete compromise of user accounts. If left unpatched, it’s like leaving the doors wide open for troublemakers to wreak havoc on your wiki! Update to XWiki versions 14.4.8, 14.10.4, or 15.0 immediately to close this vulnerability. Alternatively, apply a patch to `AppWithinMinutes.ClassEditSheet` to mitigate the risk while you work on a full update. You've got this! By taking these steps, you'll secure your wiki and protect your user community. 🛡️