-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
erroring out on html comment section #804
Comments
I wasn't able to reproduce the issue with this plugin & its debug mode active. What version of Ruby & WPScan are you using ? |
Ruby Version: ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-darwin14]
|
This is oooooooood then :x Could you run again with the -v option and then paste the stack trace of the error here/on gist/by email please ? |
Sure thing - just emailed |
Still can't reproduce in specs with your code :o When you said that your gems were up-to-date, you showed the rubygems update command (gem update --system), not the one to update all the gems (gem --update). Please do the following: |
Alternatively, you can also send us the URL of your site to see if the issue is from the code that could be before / after the Debug comments |
Ok - see below. Also - I think I included the url of my site in the email I sent you.
I ran
Should I install the missing gems? |
ah crap, |
Was able to reproduce with the full code of your homepage :) |
Interesting, I wonder why it happens on my homepage but not when trying to reproduce with the plugin. |
|
That fixed it - thanks! |
hello... im new on linux...i learn how to use wpscan.. and i have some trouble about wpscan...kenosis@kenosis-VPCSB16FG: Run
|
did you run the command |
yes.. i run bundle install on directory wpscan, so i must reinstall my gem package ? how to execute command on terminal ? to remove my gem ? |
One of the plugins that my site uses includes an HTML comment section at the end of my landing page:
WPScan is erroring out when it hits this section with:
Is there anything I can do to get past this error?
The text was updated successfully, but these errors were encountered: