wpscan - WPScan is a black box WordPress vulnerability scan

项目说明

!alt text

![Build Status]()
![Code Climate]()
![Dependency Status]()
![Docker Pulls]()

LICENSE

WPScan Public Source License

The WPScan software (henceforth referred to simply as "WPScan") is dual-licensed - Copyright 2011-2016 WPScan Team.

Cases that include commercialization of WPScan require a commercial, non-free license. Otherwise, WPScan can be used without charge under the terms set out below.

1. Definitions

1.1 "License" means this document.

1.2 "Contributor" means each indi or legal entity that creates, contributes to the creation of, or owns WPScan.

1.3 "WPScan Team" means WPScan’s core de, an updated list of whom can be found within the CREDITS file.

2. Commercialization

A commercial use is one intended for commercial ad or monetary compensation.

Example cases of commercialization are:

- Using WPScan to provide commercial managed/Software-as-a-Service services.
- Distributing WPScan as a commercial product or as part of one.
- Using WPScan as a value added service/product.

Example cases which do not require a commercial license, and thus fall under the terms set out below, include (but are not limited to):

- Penetration testers (or penetration testing organizations) using WPScan as part of their assessment toolkit.
- Penetration Testing Linux Distributions including but not limited to Kali Linux, SamuraiWTF, BackBox Linux.
- Using WPScan to test your own systems.
- Any non-commercial use of WPScan.

If you need to purchase a commercial license or are unsure whether you need to purchase a commercial license contact us - .

We may grant commercial licenses at no monetary cost at our own discretion if the commercial usage is deemed by the WPScan Team to significantly benefit WPScan.

Free-use Terms and Conditions;

3. Redistribution

Redistribution is permitted under the following conditions:

- Unmodified License is provided with WPScan.
- Unmodified Copyright notices are provided with WPScan.
- Does not conflict with the commercialization clause.

4. Copying

Copying is permitted so long as it does not conflict with the Redistribution clause.

5. Modification

Modification is permitted so long as it does not conflict with the Redistribution clause.

6. Contributions

Any Contributions assume the Contributor grants the WPScan Team the unlimited, non-exclusi to reuse, modify and relicense the Contributor's content.

7. Support

WPScan is provided under an AS-IS basis and without any support, updates or maintenance. Support, updates and maintenance may be gi to the sole discretion of the WPScan Team.

8. Disclaimer of Warranty

WPScan is provided under this License on an “as is” basis, without warranty of any kind, either expressed, implied, or statutory, including, without limitation, warranties that the WPScan is free of defects, merchantable, fit for a particular purpose or non-infringing.

9. Limitation of Liability

To the extent permitted under Law, WPScan is provided under an AS-IS basis. The WPScan Team shall never, and without any limit, be liable for any damage, cost, expense or any other payment incurred as a result of WPScan's actions, failure, bugs and/or any other interaction between WPScan and end-equipment, computers, other software or any 3rd party, end-equipment, computer or services.

10. Disclaimer

Running WPScan against websites without prior mutual consent may be illegal in your country. The WPScan Team accept no liability and are not responsible for any misuse or damage caused by WPScan.

11. Trademark

The "wpscan" term is a registered trademark. This License does not grant the use of the "wpscan" trademark or the use of the WPScan logo.

INSTALL

WPScan comes pre-installed on the following Linux distributions:

On macOS WPScan is packaged by Homebrew as wpscan.

Windows is not supported

We suggest you use our official Docker image from to avoid installation problems.

DOCKER

Start WPScan

For the a Options, please see

If you run the git of wpscan we included some binstubs in ./bin for easier start of wpscan.

Examples

Mount a local wordlist to the docker container and start a bruteforce attack for user admin

(This mounts the host directory ~/wordlists to the container in the path /wordlists)

Use logfile option

Published on

Manual install

Prerequisites

Installing dependencies on Ubuntu

sudo apt-get install libcurl4-openssl-de libxml2-de ruby-de libgmp-de

Installing dependencies on Debian

sudo apt-get install gcc git ruby ruby-de make zlib1g-dev

Installing dependencies on Fedora

sudo dnf install gcc ruby-de libxml2-de libxslt-de patch rpm-build

Installing dependencies on Arch Linux

pacman -Syu ruby
pacman -Syu libyaml

Installing dependencies on macOS

Apple Xcode, Command Line Tools and the libffi are needed (to be able to install the FFI gem), See

Installing with R when doing a manual install)

If you are using GNOME Terminal, there are some steps required before executing the commands. See here for more information:

# Install all prerequisites for your OS (look above)
cd ~
curl -sSL | gpg --import -
curl -sSL | bash -s stable
source ~/.r/rvm
echo "source ~/.r/rvm" >> ~/.bashrc
r 2.4.2
rvm use 2.4.2 --default
echo "gem: --no-ri --no-rdoc" > ~/.gemrc
git clone
cd wpscan
gem install bundler
bundle install --without test

Installing manually (not recommended)

git clone
cd wpscan
sudo gem install bundler && bundle install --without test

KNOWN ISSUES

- Typhoeus segmentation fault

Update cURL to => 7.21 (may have to install from source)

- Proxy not working

Update cURL to => 7.21.7 (may have to install from source).

Installation from sources :

Grab the sources from
Decompress the archive
Open the folder with the extracted files
Run ./configure
Run make
Run sudo make install
Run sudo ldconfig

- cannot load such file -- readline:

sudo aptitude install libreadline5-de

Then, open the directory of the readline gem (you have to locate it)

cd ~/.rvm/src/ruby-XXXX/ext/readline
ruby extconf.rb
make
make install

See for more details

- no such file to load -- rubygems

And select your ruby

See

WPSCAN ARGUMENTS

--update Update the database to the latest .
--url | -u <target url> The WordPress URL/domain to scan.
--force | -f Forces WPScan to not check if the remote site is running WordPress.
--enumerate | -e [option(s)] Enumeration.
option :
u usernames from id 1 to 10
u[10-20] usernames from id 10 to 20 (you must write [] chars)
p plugins
vp only plugins
ap all plugins (can take a long time)
tt timthumbs
t themes
vt only themes
at all themes (can take a long time)
Multiple are allowed : "-e tt,p" will enumerate timthumbs and plugins
If no option is supplied, the default is "vt,tt,u,vp"

--exclude-content-based "<regexp or string>"
Used with the enumeration option, will exclude all occurrences based on the regexp or string supplied.
You do not need to provide the regexp delimiters, but you must write the quotes (simple or double).
--config-file | -c <config file> Use the specified config file, see the example.conf.json.
--user-agent | -a <User-Agent> Use the specified User-Agent.
--cookie <string> String to read cookies from.
--random-agent | -r Use a random User-Agent.
--follow-redirection If the target url has a redirection, it will be followed without asking if you wanted to do so or not
--batch Never ask for user input, use the default behaviour.
--no-color Do not use colors in the output.
--log [filename] Creates a log.txt file with WPScan's output if no filename is supplied. Otherwise the filename is used for logging.
--no-banner Prevents the WPScan banner from being displayed.
--disable-accept-header Prevents WPScan sending the Accept HTTP header.
--disable-referer Prevents setting the Referer header.
--disable-tls-checks Disables SSL/TLS certificate .
--wp-content-dir <wp content dir> WPScan try to find the content directory (ie wp-content) by scanning the index page, however you can specify it.
Subdirectories are allowed.
--wp-plugins-dir <wp plugins dir> Same thing than --wp-content-dir but for the plugins directory.
If not supplied, WPScan will use wp-content-dir/plugins. Subdirectories are allowed
--proxy <[protocol://]host:port> Supply a proxy. HTTP, SOCKS4 SOCKS4A and SOCKS5 are supported.
If no protocol is given (format host:port), HTTP will be used.
--proxy-auth <username:password> Supply the proxy login credentials.
--basic-auth <username:password> Set the HTTP Basic authentication.
--wordlist | -w <wordlist> Supply a wordlist for the password brute forcer.
If the "-" option is supplied, the wordlist is expected .
--username | -U <username> Only brute force the supplied username.
--usernames <path-to-file> Only brute force the usernames from the file.
--cache-dir <cache-directory> Set the cache directory.
--cache-ttl <cache-ttl> Typhoeus cache TTL.
--request-timeout <request-timeout> Request Timeout.
--connect-timeout <connect-timeout> Connect Timeout.
--threads | -t <number of threads> The number of threads to use when multi-threading requests.
--max-threads <max-threads> Maximum Threads.
--throttle <milliseconds> Milliseconds to wait before doing another web request. If used, the --threads should be set to 1.
--help | -h This help screen.
-- | -v output.
-- Output the current and exit.

WPSCAN EXAMPLES

Do 'non-intrusive' checks...

Do wordlist password brute force on enumerated users using 50 threads...

Do wordlist password brute force on enumerated users using STDIN as the wordlist...

Do wordlist password brute force on the 'admin' username only...

Enumerate installed plugins...

Run all enumeration tools...

Use custom content directory...

Update WPScan's databases...

Debug output...

PROJECT HOME

DATABASE

GIT REPOSITORY

ISSUES

WPScan issues

DE DOCUMENTATION

Download and Clone

> Clone: git clone

The404Hacking | Digital UnderGround Team

Follow us !

Instagram - GitHub

YouTube - Aparat

项目信息

开发语言：Ruby

Star 数：11

技术要点

该项目属于安全软件方向的开源资源，代码结构清晰，适合安全研究人员学习参考。项目围绕WPScan is a black box WordPress vulnerability scanner.展开，提供了可运行的实现，对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。

从技术实现角度看，此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论，梳理项目的初始化流程、核心模块职责与数据流转，逐步掌握其中的技术细节与设计思路。

使用与学习建议

1. 下载源码压缩包，解压到本地环境。

2. 根据项目类型准备对应的运行环境与依赖。

3. 按照 README 中的步骤完成配置与部署。

4. 在隔离的测试环境中运行验证，避免影响生产系统。

免责声明

本资源来源于开源社区，仅供安全研究、技术学习与合法授权范围内的攻防演练使用，请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。