This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Vbulletin
The Admin CP in vBulletin 5.6.3 allows XSS via a Junior Member Title to User Title Manager. (2020-09-03, CVE-2020-25117)
The Admin CP in vBulletin 5.6.3 allows XSS via a Rank Type to User Rank Manager. (2020-09-03, CVE-2020-25122)
The Admin CP in vBulletin 5.6.3 allows XSS via a Smilie Title to Smilies Manager. (2020-09-03, CVE-2020-25123)
The Admin CP in vBulletin 5.6.3 allows XSS via a Style Options Settings Title to Styles Manager. (2020-09-03, CVE-2020-25118)
The Admin CP in vBulletin 5.6.3 allows XSS via a Title of a Child Help Item in the Login/Logoff part of the User Manual. (2020-09-03, CVE-2020-25119)
The Admin CP in vBulletin 5.6.3 allows XSS via an admincp/attachment.php&do=rebuild&type= URI. (2020-09-03, CVE-2020-25124)
The Admin CP in vBulletin 5.6.3 allows XSS via an Announcement Title to Channel Manager. (2020-09-03, CVE-2020-25116)
The Admin CP in vBulletin 5.6.3 allows XSS via an Occupation Title or Description to User Profile Field Manager. (2020-09-03, CVE-2020-25115)
The Admin CP in vBulletin 5.6.3 allows XSS via the admincp/search.php?do=dosearch URI. (2020-09-03, CVE-2020-25120)
The Admin CP in vBulletin 5.6.3 allows XSS via the Paid Subscription Email Notification field in the Options. (2020-09-03, CVE-2020-25121)
Why Cross-site Scripting can be dangerous
Cross site scripting is an attack where a web page executes code that is injected by an adversary. It usually appears, when users input is presented. This attack can be used to impersonate a user, take over control of the session, or even steal API keys.
The attack can be executed e.g. when you application injects the request parameter directly into the HTML code of the page returned to the user:
https://server.com/confirmation?message=Transaction+Complete
what results in:
<span>Confirmation: Transaction Complete</span>
In that case the message can be modified to become a valid Javascript code, e.g.:
https://server.com/confirmation?message=<script>dangerous javascript code here</script>
and it will be executed locally by the user's browser with full access to the user's personal application/browser data:
<span>Confirmation: <script>dangerous javascript code here</script></span>