Open gnuletik opened 5 months ago
When running wpscan with an old database, the following message should be printed:
https://github.com/wpscanteam/wpscan/blob/2613fdcc6b22ac7581f3aeb7f33447e3d8417f6c/app/controllers/core.rb#L40
To reproduce, I set on old date in the ~/.wpscan/db/.last_update file.
~/.wpscan/db/.last_update
The message should have been printed.
It seems to be the same issue as https://github.com/wpscanteam/wpscan/issues/1724 but no solution was found.
As you can see, the message is not printed.
$ wpscan --url https://localhost _______________________________________________________________ __ _______ _____ \ \ / / __ \ / ____| \ \ /\ / /| |__) | (___ ___ __ _ _ __ ® \ \/ \/ / | ___/ \___ \ / __|/ _` | '_ \ \ /\ / | | ____) | (__| (_| | | | | \/ \/ |_| |_____/ \___|\__,_|_| |_| WordPress Security Scanner by the WPScan Team Version 3.8.25 Sponsored by Automattic - https://automattic.com/ @_WPScan_, @ethicalhack3r, @erwan_lr, @firefart _______________________________________________________________ [i] It seems like you have not updated the database for some time.
Subject of the issue
When running wpscan with an old database, the following message should be printed:
https://github.com/wpscanteam/wpscan/blob/2613fdcc6b22ac7581f3aeb7f33447e3d8417f6c/app/controllers/core.rb#L40
Your environment
Steps to reproduce
To reproduce, I set on old date in the
~/.wpscan/db/.last_update
file.Expected behavior
The message should have been printed.
It seems to be the same issue as https://github.com/wpscanteam/wpscan/issues/1724 but no solution was found.
Actual behavior
As you can see, the message is not printed.
What have you already tried