Wpscan: Update database error

Created on 26 Sep 2017 · 7Comments · Source: wpscanteam/wpscan

Hi,

Ran wpscan and it said to report it as GitHub issue, so here goes:

[i] It seems like you have not updated the database for some time.
[?] Do you want to update now? [Y]es [N]o [A]bort, default: [N]y
[i] Updating the Database ...
[!] wp_versions.xml: checksums do not match (local: 3dc8f537d1442ea8b439fa9942d062570bc5ad7d2703b6776604fd75b3cb6e1817de66091fc2a2ee5bdfa6db7202ea48b9b5e7b94543c377c805fe9b9b92aacf remote: 7906a077aca2056c0a429664655b577db886cfbc3b3dbb6cd8d53a767ab680cce407c1b6cb4823e2aa6c26d19c0c91a3349ecb43a29024151fd0356561f82a5e)
[!] Downloaded File Content:

4.6.3
.........

[!] Please submit this info as an Github issue

Source

CoreISP

👍1

Most helpful comment

This should be fixed now if you try to update

erwanlr on 27 Sep 2017

🎉3

All 7 comments

Did you try to update another time ? Sometimes bad connection can have such effect and re-run the update again does it

erwanlr on 26 Sep 2017

Hi erwanlr,

Aye I ran it three times or something before giving up.
I just tried it again (after installing HS) and it works OK now by the looks of it.

Guess false alarm. :)

CoreISP on 26 Sep 2017

I am experiencing the same issue.
Here is my console output:

$ ruby wpscan.rb --update --verbose
_______________________________________________________________
        __          _______   _____                  
        \ \        / /  __ \ / ____|                 
         \ \  /\  / /| |__) | (___   ___  __ _ _ __ ®
          \ \/  \/ / |  ___/ \___ \ / __|/ _` | '_ \ 
           \  /\  /  | |     ____) | (__| (_| | | | |
            \/  \/   |_|    |_____/ \___|\__,_|_| |_|

        WordPress Security Scanner by the WPScan Team 
                       Version 2.9.4-dev
          Sponsored by Sucuri - https://sucuri.net
   @_WPScan_, @ethicalhack3r, @erwan_lr, pvdl, @_FireFart_
_______________________________________________________________

[i] Updating the Database ...
[+] Checking local_vulnerable_files.xml
  [i] Already Up-To-Date
[+] Checking local_vulnerable_files.xsd
  [i] Already Up-To-Date
[+] Checking timthumbs.txt
  [i] Already Up-To-Date
[+] Checking user-agents.txt
  [i] Already Up-To-Date
[+] Checking wp_versions.xml
  [i] Needs to be updated
  [i] Backup Created
  [i] Downloading new file
  [i] Downloaded File Checksum: 7906a077aca2056c0a429664655b577db886cfbc3b3dbb6cd8d53a767ab680cce407c1b6cb4823e2aa6c26d19c0c91a3349ecb43a29024151fd0356561f82a5e
  [i] Database File Checksum  : 49e0437d7775f2dbe692265b8b0488be035d49fe44086c7225ebb6852537d892838ed9be70cc8474c29cf9eb4ec015d22dc2623dbf494023ddf7787038b95a1b
  [i] Restoring Backup due to error
  [i] Deleting Backup
[!] wp_versions.xml: checksums do not match (local: 7906a077aca2056c0a429664655b577db886cfbc3b3dbb6cd8d53a767ab680cce407c1b6cb4823e2aa6c26d19c0c91a3349ecb43a29024151fd0356561f82a5e remote: 49e0437d7775f2dbe692265b8b0488be035d49fe44086c7225ebb6852537d892838ed9be70cc8474c29cf9eb4ec015d22dc2623dbf494023ddf7787038b95a1b)
[!] Current Version: 2.9.4-dev
[!] Downloaded File Content:
<?xml version="1.0" encoding="UTF-8"?>
<!--
  This file contains identification data to identify WordPress versions.
  http://wordpress.org/download/release-archive/

  Position is important, DO NOT change anything unless you know what you are doing :p
-->
<wp-versions xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="wp_versions.xsd">

  <file src="readme.html">
    <hash md5="997cfaa41d14c329574ab63128a6d8ef">
      <version>4.6.3</version>
    </h
.........
  <hash md5="f786f66d3a40846aa22dcdfeb44fa562">
      <version>2.0</version>
    </hash>
  </file>

  <file src="wp-layout.css">
    <hash md5="7140e06c00ed03d2bb3dad7672557510">
      <version>1.2.1</version>
    </hash>
    <hash md5="1bcc9253506c067eb130c9fc4f211a2f">
      <version>1.2-delta</version>
    </hash>
  </file>

  <file src="layout2b.css">
    <hash md5="baec6b6ccbf71d8dced9f1bf67c751e1">
      <version>0.71-gold</version>
    </hash>
  </file>

</wp-versions>

[!] Some hints to help you with this issue:
[!] -) Try updating again using --verbose
[!] -) If you see SSL/TLS related error messages you have to fix your local TLS setup
[!] -) Windows is still not supported