Back to list
XSS in admin logs - vBulletin 3.7.2 and lower, vBulletin 3.6.10 PL2 and lower
Jul 08 2008 04:59PM
Jessica Hope (jessicasaulhope googlemail com)
Advisory : XSS in admin logs
Release Date : July 06th 2008
Application : vBulletin
Version : vBulletin 3.7.2 and lower, vBulletin 3.6.10 PL2 and lower
Platform : PHP
Vendor URL : http://www.vbulletin.com/
Authors : Jessica Hope (jessicasaulhope (at) googlemail (dot) com [email concealed]),
Friends who wish to remain anonymous.
Due to various failures in sanitising user input, it is possible to
construct XSS attacks that are rather damaging.
The XSS in question exists on the log viewing page of the admin control panel.
When a missing page is requested, a log is created in the admin area, however
the inputs to this log lack sanitation. The script name is taken from
basename(PHP_SELF), while the action is taken from _REQUEST['do']. Either one
can be used for introducing XSS vectors.
To highlight the severity and underline the fact that his vulnerability is
<img src="http://localhost/vB/upload/admincp/faq.php/0?do=<script>/*" />
<!--edit to match your data -->
<img src="http://localhost/vB/upload/admincp/faq.php/5?do=*/e%3D''/*" />
<!-- end edit -->
<img src="http://localhost/vB/upload/admincp/faq.php/7?do=*/g%3D't>%22)'/*" />
<img src="http://localhost/vB/upload/admincp/faq.php/9?do=*/eval(h)/*" />
<img src="http://localhost/vB/upload/admincp/faq.php/a0?do=*/</script>" />
You then need to send the admin to
and the XSS will render.
The limits on the XSS:
basename(PHP_SELF) is 50 characters max and no slashes
_REQUEST['do'] is limited to 20 characters, but no character restriction.
The tight character limits on the unsanitized parameters are not
mitigating the severity, as unlimited
attack space can be obtained as shown above.
As per my last exploits, all XSS in the vBulletin ACP can be used for
PHP injection instantly. This
is due to the design of the vBulletin hooks feature. As this
particular XSS is persistent and will
render in all major browsers it is particularly dangerous.
Update to vBulletin 3.7.2 PL1 or vBulletin 3.6.10 PL3
Don't trust PHP_SELF and sanitise all data that is going to be
displayed to the user
[ reply ]
Copyright 2010, SecurityFocus