-
AuthorPosts
-
January 31, 2017 at 11:38 am #740564
Wordfence alerts me this:
It seems that a bad link is found in that file, opening the file the link is in a commented row.
It should not have been edited since i installed the theme, can someone helps me to understand if it is normal?Thank you
January 31, 2017 at 11:49 am #740569I have exactly the same message from Wordfence on one of my enfold sites this morning.
I assume it is a false positive but would like to get feedback from the Enfold support team as soon as possible. I have run the site through sucuri’s external site check scan and it comes back clean.The site is: http://stewkley.org.uk
Waiting to hear ?
January 31, 2017 at 11:57 am #740572the same here :( Must i do anything ?
January 31, 2017 at 12:02 pm #740575I’m having the same issue on multiple websites.
What am I to do?January 31, 2017 at 12:04 pm #740576As I mentioned in another topic about this problem:
Same problem. Seems like the link they use got hacked. The link (http://www.link.at/) DON’T VISIT ATM is mentioned as a comment.
//fallback for previous default input link elements: convert a http://www.link.at value to a manually entry
if(strpos($element[‘std’], ‘http://’) === 0) $element[‘std’] = ‘manually,’.$element[‘std’];Nothing to worry about as long as you don’t visit the website. Most browsers will block the site anyways.
January 31, 2017 at 12:09 pm #740580Any response or comment from author?
January 31, 2017 at 12:22 pm #740583It can be a concern as Google can blacklist your site if it finds the link when crawling to index etc.
January 31, 2017 at 1:16 pm #740603Same issue here too.
January 31, 2017 at 1:36 pm #740608Hey!
Please go to enfold/config-templatebuilder/avia-template-builder/php/html-helper.class.php file and find
//fallback for previous default input link elements: convert a http://www.link.at value to a manually entry
and change it to
//fallback for previous default input link elements: convert a http://kriesi.at value to a manually entry
We have informed our devs :)
Edit: We will add the changes in upcoming Enfold update. Link is in commented line therefore it has no affect whatsoever however applying these changes will take care of Wordfence alert
Regards,
Yigit- This reply was modified 7 years, 10 months ago by Yigit.
January 31, 2017 at 1:37 pm #740609I have temporarily substituted the bad URL for a good one in the html-helper.class.php file.
Re-scanned with WORDFENCE – no problem.
Not saying this is a 100% solution, but it will stop any poss blacklisting for now!January 31, 2017 at 1:44 pm #740611Hey!
We will update the file in upcoming Enfold version. Link is in commented line therefore has no affect but still changing it should get rid of the alert :)
We would appreciate it if you could please test it and confirm :)Regards,
YigitJanuary 31, 2017 at 1:51 pm #740617Yep, replacing that link results in a clear Wordfence scan. Thank you Yigit
By the way, for anyone else looking for it it is located at line 726 in the file.
Hugues
January 31, 2017 at 1:52 pm #740619Hi,
Great! Thanks for confirming and glad it worked for you! :)
We will keep the thread open and will wait to hear from the creator of this thread. If you have any other questions or issues, please feel free to start a new thread.
Best regards,
YigitJanuary 31, 2017 at 1:52 pm #740620done, thank you.
January 31, 2017 at 1:54 pm #740621All clear here :-)
January 31, 2017 at 2:04 pm #740625 -
AuthorPosts
- The topic ‘Wordfence found a suspected malware in an Enfold .php file’ is closed to new replies.