Thanks for sharing this, Peter. Normally they email us if they have something reported, but we didn’t get any notification from them about this, so thanks for letting us know. Maybe it was because of the low severity. Either way, we’ll take a look at it and make any necessary updates.
-
This reply was modified 1 year, 1 month ago by
jaysupport.
Thread Starter
Peter
(@hardpeter4u)
Hi,
Just letting you know the same vulnerability still exists in the updated version 1.3.4
Thanks,
Peter
Yes, because that update was just to mark that the plugin has been tested and is compatible with WordPress 6.8. We are working now on an update that includes a few other elements and that will also include a patch for the issue reported.
Thread Starter
Peter
(@hardpeter4u)
Ok, thanks for your reply. Didn’t mean to bother you.
I appreciate it!!
Peter
It’s still open in Version 1.3.6. When do you plan to fix this?
@alexqbox Not the same issue. An update was just released for what you’re referencing.
Ah ok, thanks and sorry for the confusion.