wpscanteam /wpscan
WPScan WordPress security scanner. Written for security professionals and blog maintainers to test the security of their WordPress websites. Contact us via [email protected]
★ 9,853⑂ 1,349👁 255⑃ 602● 1,479▤ 70
+0
日增长
9,853
stars
1,349
forks
255
watchers
602
prs
1,479
issues
70
releases
README
WPScan WordPress Security Scanner WPScan WordPress Vulnerability Database - WordPress Security Plugin INSTALL Prerequisites - (Optional but highly recommended: rbenv) - Ruby = 3.3 - Recommended: latest stable - Curl = 7.72 - Recommended: latest stable - The 7.29 has a segfault - The < 7.72 could result in Stream error in the HTTP/2 framing layer in some cases - RubyGems - Recommended: latest stable - Nokogiri might require packages to be installed via your package manager depending on your OS, see https://nokogiri.org/tutorials/installing_nokogiri.html In a Pentesting distribution When using a pentesting distribution (such as Kali Linux), it is recommended to install/update wpscan via the package manager if available. In macOSX via Homebrew shell brew install wpscanteam/tap/wpscan From RubyGems WPScan depends on gems with native extensions (e.g. yajl-ruby, nokogiri, ffi), so a working C toolchain and Ruby development headers must be present before gem install wpscan. Without them, the install fails with errors like Failed to build gem native extension or make: x86_64-linux-gnu-gcc: No such file or directory (see 1844). - Debian / Ubuntu: shell sudo apt install build-essential ruby-dev - Fedora / RHEL / CentOS: shell sudo dnf install @development-tools ruby-devel - Arch Linux: shell sudo pacman -S base-devel ruby - Alpine: shell sudo apk add build-base ruby-dev - macOS: install the Xcode Command Line Tools (xcode-select --install). Then install the gem: shell gem install wpscan On MacOSX, if a Gem::FilePermissionError is raised due to Apple's System Integrity Protection (SIP), either install RVM and install wpscan again, or run sudo gem install -n /usr/local/bin wpscan (see 1286) Updating You can update the local database by using wpscan --update Updating WPScan itself is either done via gem update wpscan or the packages manager (this is quite important for distributions such as in Kali Linux: apt-get update && apt-get upgrade) depending on how WPScan was (pre)installed Docker Pull the repo with docker pull wpscanteam/wpscan Enumerating usernames shell docker run -it --rm -v wpscan-db:/wpscan/.cache/wpscan/db wpscanteam/wpscan --url https://target.tld/ --enumerate u Enumerating a range of usernames shell docker run -it --rm -v wpscan-db:/wpscan/.cache/wpscan/db wpscanteam/wpscan --url https://target.tld/ --enumerate u1-100 replace u1-100 with a range of your choice. Persisting the local database The image ships with a copy of the local database baked in at build time. Because the example commands above use --rm, any database update performed during a run is discarded when the container exits, so the next run starts again from the (potentially stale) baked-in copy. Mounting a named volume at /wpscan/.cache/wpscan/db (the wpscan user's cache directory inside the container) keeps the database across runs, so wpscan --update only re-downloads files wh
Latest release
v4.2.0 v4.2.0 2026-10-27What's Changed Added --max-response-size MiB caps how much of any response is read (default 16 MiB, 0 disables), guarding against memory exhaustion on targets serving huge or endless responses by @gnuletik in https://github.com/wpscanteam/wpscan/pull/2091 Changed Responses larger than 16 MiB are now truncated by default. Use --max-response-size 0 to restore the previous unbounded behavior. by @gnuletik in https://github.com/wpscanteam/wpscan/pull/2091 SARIF now reports aborted runs as unsuccessful, with the abort reason in toolExecutionNotifications. Consumers will show an aborte