In the case pointed out by Michal_W, there is a problem with the handling of the second argument.
According to MDN Web Docs, the second argument is defined as "A string or any other object with a stringifier".
On the other hand, the WebAdviser implementation assumes that it is a string and calls the startsWith method, so an error occurs if the second argument is an object that does not have a startsWith method.
This is a really poor implementation.
The problem with my logs from the site appeared on January 13.
So you can't fix one js file in 4 days? Are you serious?
This is a critical issue that affects all the sites your users visit!
Do you understand this at all?
Why do I need to create an account to report that I have the same problem ?
The extension breaks my site, which is not okay...
What "page_crypto_mining" has to do with web advisor ? Isn't the name suspicious ?
Do you have any estimating time to fix the problem ?
Hey @Edward_Franso, thank you for keeping the community up to date and for the workaround information. I saw that 126.96.36.19980 was released on the Google Chrome Web Store this morning. Can you confirm if this contains the fix for this reported issue or provide a link to a change log where we can monitor?
Greetings From McAfee.
The issue has been resolved. Kindly uninstall the existing WebAdvisor extension and install the latest version from the chrome web store.
If you have any concerns, contact our support team using the link below.
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: