OWASP VBScan Project
OWASP VBScan Tool Project
VBScan is an opensource project in perl programming language to detect VBulletin CMS vulnerabilities and analyses them.
Why VBScan ?
If you want to do a penetration test on a vBulletin Forum, VBScan is Your best shot ever! This Project is being faster than ever and updated with the latest VBulletin vulnerabilities.
VBScan is an opensource project in perl programming language to detect VBulletin CMS vulnerabilities and analyses them.This Project is being faster than ever and updated with the latest VBulletin vulnerabilities.
GNU GENERAL PUBLIC LICENSE , Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. http://fsf.org/ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Click to see the full license
The OWASP Security Principles are licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
News and Events
The OWASP Tool Project Template is developed by a worldwide team of volunteers. A live update of project contributors is found here.
The first contributors to the project were:
This project is going to be the best VBulletin scanner, it could be handle in ZAP and/or get develop to a single scanner, At the end We could have a forum cms penetration tester which is updated with the last vulnerabilities.
This Project was created to be a VBScanner which already it is and now need to be best with some tasks:
- Optimize software core to be fast and easy to develop
- make it module base and create libraries for developers
- Support all OS
- Be update with latest exploits.
- Create documents for newbie users
- Keep testing and fix bugs!
Please submit your feedbacks and issues in HERE.
- What do like?
- What don't you like?
- What features would you like to see prioritized on the roadmap?
- Do you have any problem with tool?
- Do you need any exploit to be add?
This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern. Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap. And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category.
The Tool Project Template must specify the minimum set of tabs a project should have, provide some an example layout on each tab, provide instructional text on how a project leader should modify the tab, and give some example text that illustrates how to create an actual project.
It would also be ideal if the sample text was translated into different languages.
This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager. Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project
| PROJECT INFO
What does this OWASP project offer you?
| RELEASE(S) INFO|
What releases are available for this project?