Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author YARPP

    (@jeffparker)

    Hi @kbwebpro

    Thank you for the positive words. We’re working on resolving the issue. Unfortunately, we weren’t notified by the reporting party, which is the standard practice before any vulnerability is published. We have since reached out to them and are awaiting details on how to replicate the bug. For those interested, you can track our progress on this issue here: https://wordpress.org/support/topic/update-713/. As noted by the reporter, this issue has “a low severity impact and is unlikely to be exploited.”  Details in the link.

    Plugin Author YARPP

    (@jeffparker)

    Hi @kbwebpro We are pleased to share that the issue has been resolved in version 5.30.11, and both Patchstack and Wordfence have verified the patch, marking it as fixed. We’re committed to keeping the plugin secure and reliable, and your support makes a huge difference. Thanks again for your patience and support!

    @kbwebpro please consider updating the title of this page as it implies there is a “security flaw”.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this review.