Viewing 4 replies - 1 through 4 (of 4 total)
  • Brhum

    (@brhum)

    Yes. This is critical. I have disabled Amelia but the infected file pointing to the compromised domain is still on my server. Only a matter of time before Google blocks my domain as a security threat.

    webulu

    (@webulu)

    Yes Up.

    Your customers, our customers, their safety, their work and ultimately your reputation is at stake, please take all necessary measures urgently.

    I am deactivating Amelia too. Please do something ASAP

    Plugin Author ameliabooking

    (@ameliabooking)

    Hello,

    We checked with our developers and there is nothing wrong with Amelia despite WordFence showing warnings.

    That line of code is turned on if the “Enable usage for older IE browsers” setting is turned on… That setting has been turned off by default for about 2 years, so it must be turned on manually in order for this allegedly problematic JS to appear on the page. Our developers will work on removing it completely in one of the next updates. We will completely remove the call to that JS polyfill script and that warning should no longer appear.

    If you have Enable usage for older IE browsers turned on in settings activations, just turn it off and make sure to purge the cache, and this should not appear anymore. In the event that it continues to appear as you mentioned, there is nothing wrong with Amelia that would harm your site or similar, and in one of the next updates, very possibly in the next one, we hope that our developers will remove that string and this warning should no longer appear. appears

    I wanted to bring to your attention that when the settings are turned off, JavaScript (JS) will not be invoked on the page. However, Wordfence will still detect the presence of a supposedly Amelia issue with code, likely based on identifying that specific string. Therefore, even if you have disabled this option, you may still be able to identify the issue.  Rest assured, we plan to address this with an upcoming update scheduled for following week, tentatively on Tuesday, where we will ensure that JS is not called to the page. Thank you for your attention to this matter. Best regards.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.