Pull wpscan metadata.json on repo

[bpce-it-dis-soc-sof]

In our environment, our proxy does not allow wpscan.org, so running wpscan fails with:
[ERR] wordpress.wpscan Unable to get https://data.wpscan.org/metadata.json.sha512 (SSL peer certificate or SSH remote key was not OK)

I think it should be doable to pull this into the GitHub repo as a fallback ?

[Initsogar]

Hi 👋

I don't think putting the database files in the GitHub repo would be the best fallback. They need to stay fresh and match their checksums, so maintaining another public copy would add some operational and distribution concerns.

A better option may be to make the database base URL configurable, so environments like yours can mirror https://data.wpscan.org/ internally and point WPScan at that mirror while keeping checksum verification.

In the meantime, I'd really encourage allowlisting data.wpscan.org if your proxy policy allows it, since it's WPScan's data source and the cleanest fix for a tool you're using. Otherwise, you can pre-populate the local database directory and run with --no-update.

[ERR] wordpress.wpscan Unable to get https://data.wpscan.org/metadata.json.sha512 (SSL peer certificate or SSH remote key was not OK)

Also, could you also confirm whether wpscan --update --disable-tls-checks changes the error? That would help tell whether this is a proxy block or TLS interception issue.

[ArSn]

Of course I don't know your exact configuration, but could you use the --proxy-target-only option? Only works if you have internet access without using the proxy, of course.