scanner-wpscan
10K+
OWASP secureCodeBox is an automated and scalable open source solution that can be used to integrate various security vulnerability scanners with a simple and lightweight interface. The secureCodeBox mission is to support DevSecOps Teams to make it easy to automate security vulnerability testing in different scenarios.
With the secureCodeBox we provide a toolchain for continuous scanning of applications to find the low-hanging fruit issues early in the development process and free the resources of the penetration tester to concentrate on the major security issues.
The secureCodeBox project is running on Kubernetes. To install it you need Helm, a package manager for Kubernetes. It is also possible to start the different integrated security vulnerability scanners based on a docker infrastructure.
You can find resources to help you get started on our documentation website including instruction on how to install the secureCodeBox project and guides to help you run your first scans with it.
latest (represents the latest stable release build)3.0.0, 2.9.0, 2.8.0, 2.7.0This scanner image is intended to work in combination with the corresponding parser image to parse the scanner findings to generic secureCodeBox results. For more information details please take a look at the project page or [documentation page][https://www.securecodebox.io/docs/scanners/WPScan].
docker pull securecodebox/scanner-wpscan
WPScan is a free, for non-commercial use, black box WordPress vulnerability scanner written for security professionals and blog maintainers to test the security of their sites.
NOTE: You need to provide WPSan with an API Token so that it can look up vulnerabilities infos with https://wpscan.com. Without the token WPScan will only identify WordPress Core / Plugin / Theme versions but not if they are actually vulnerable. You can get a free API Token at by registering for an account at https://wpscan.com. Using the secureCodeBox WPScans you can specify the token via the
WPVULNDB_API_TOKENtarget attribute, see the example below.
To learn more about the WPScan scanner itself visit wpscan.org.
The following security scan configuration example are based on the WPScan Documentation, please take a look at the original documentation for more configuration examples.
wpscan --url example.com -e vp --plugins-detection mixed --api-token WPVULNDB_API_TOKENwpscan --url example.com -e ap --plugins-detection mixed --api-token WPVULNDB_API_TOKENwpscan --url example.com -e u --passwords /path/to/password_file.txtwpscan --update--plugins-detection option.-e option.Available Choices:
vp | Vulnerable plugins
ap | All plugins
p | Plugins
vt | Vulnerable themes
at | All themes
t | Themes
tt | Timthumbs
cb | Config backups
dbe | Db exports
u | User IDs range. e.g: u1-5
Range separator to use: '-'
Value if no argument supplied: 1-10
m | Media IDs range. e.g m1-15
Note: Permalink setting must be set to "Plain" for those to be detected
Range separator to use: '-'
Value if no argument supplied: 1-100
Separator to use between the values: ','
Default: All Plugins, Config Backups
Value if no argument supplied: vp,vt,tt,cb,dbe,u,m
Incompatible choices (only one of each group/s can be used):
- vp, ap, p
- vt, at, t
You are welcome, please join us on... 👋
secureCodeBox is an official OWASP project.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.
Content type
Image
Digest
sha256:2eda22b39…
Size
80 MB
Last updated
8 days ago
docker pull securecodebox/scanner-wpscan:sha-5f6bcc8Pulls:
123
Jun 29 to Jul 5