In reply to Marcelo.

You should reach out to those plugin developers. Hopefully, they managed to hear about this issue sooner than their customers and have their plugin updated to fix this vulnerability.