How exposed is the plugin and does it need to be patched? Our team disabled it to prevent problems over the weekend, but would be great to know if we can re-enable it.
I appreciate the response and letting us know about the update. However, it has come to our attention that there are also log4j vulnerabilities with version 2.16 and that 2.17 is now available. Have you investigated whether or not the plugin needs another log4j update?