Releases: wpscanteam/wpscan
Releases · wpscanteam/wpscan
v3.8.17
- Minor:
- When checking the full response during Enumeration,
valid_response_codes
are now also considered
--exclude-usernames
option added
v3.8.16
- Minor:
introduced_in
field returned by the API is now handled
- Fixed Incorrect required long option value when an error is raised - Ref wpscanteam/OptParseValidator#84
v3.8.15
- Minor:
- Updated number of daily free API requests in the output
v3.8.14
- Minor:
- Fixed exception raised in rescue statement when error happened in OptParseValidator, causing multiple stacktraces to be displayed rather than the error message.
- DB Export pattern updated to detect file with
CREATE/ALTER DATABASE
statements - Ref #1599
v3.8.13
- Minor:
- Target URL added to the JSON output when an error occurs before
controller#run
- Ref #1594
--force
option added to scan target despite returning a 403 when checking its availability - Ref #1592
- Add an InterestingFinding check (
php_disabled
) to detect whether or not PHP is disabled - Ref #1593
v3.8.12
- Minor:
- Updated dependencies. Installation should be faster and easier regarding Nokogiri
v3.8.11
- Minor:
- Updated ruby to 2.7.2
- Updated some leftover of wpscan.org to the correct domain/URL
- Updated some leftover of WPVulnDB to the correct name
- Fixed API retry not properly working due to caching
- Fixed incorrect detection of an invalid API Token provided #1579
v3.8.10
- Minor:
- Added a
login-uri
CLI option to set the URI of the login page (if different from wp-login.php
) - Ref #1554
v3.8.8
Minor:
- All links to wpvulndb.com have been updated to wpscan.com