nv_yvr

Thanks for doing that!

Looks like 4.9.4 did the trick!

WordPress vulnerability database now shows it as fixed!

• This reply was modified 1 year, 9 months ago by nv_yvr.

It’s been a few days, but weirdly enough, the links in my first post still show the vulnerability as not fixed.

So I’m wondering if Rico would need to contact one or both of them, for his nice plugin to be taken off their vulnerability listings?

Just for convenience, here are the links again:

Wordfence bulletin

WordPress vulnerability database

After reading this thread (and the other one), I contacted 1&1 yesterday and this morning received a reply from 1&1 acknowledging the false positive in their malware database. In their response they say they’ve now removed that false positive pattern. And their email also stated “The EWWW Image Optimizer is safe to use.”

Thanks Kimberly and Adam! That seemed to do the trick for me, too. Since the path and filename are split across two posts above: here’s the full path/file:

… /wp-content/plugins/w3-total-cache/lib/W3/Plugin/TotalCache.php

Hi RPS team! Thanks so much for your informative response – it’s much appreciated and I’ve hence successfully updated our site.

Just a little side note: Your explanation sounds perfectly suitable for the change log. In my view, having such an update signals a couple of really good things about your plugin: quality of plugin code and that the plugin is still supported.

And mentioning that in the change log should nothing but strengthen your existing and potential users’ confidence in your plugin.

Thanks again for your really useful plugin!