Hi @ptaubman
Thank you for pointing us to this. We are in the process of gathering information and details about this report so that we can best handle as soon as possible.
Keep an eye out for available updates as we get them handled and ready for everyone.
Also waiting on this fix….
We’re working on getting information about details for the reported issues, so that we can actively address the concerns. Right now we just have a report that there is an issue, but no details what or where. Keep an eye on available updates, as that will be the first place that gets notified of an update and changelog for what got addressed.
We’ll do what we can to circle back around to this thread as well.
Any updates on a patch for this? Or should we uninstall it for security reasons?
Thanks.
Still working with the appropriate people to get information of what’s been reported. No news just yet, thank you for your patience.
We don’t presently believe there’s need to deactivate/uninstall/etc based on what Patchstack shows above and patchstack is thus far reporting no known exploits thus far.
Chiming in that we got the information we needed and code changes are presently in internal review.
You should see a version 2.4.3 released soon, which addresses the reported issues.
