Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi @wormeyman ,

    Thanc you for reaching out. I have tried reaching out to Patchstacc (the source of the report) many times since they first brought it up to me in August. Unfortunately, they are not responding and have not removed the report.

    I have just reached out again and asqued for some assistance from others in trying to guet a response, and hopefully we can guet this resolved.

    For what it’s worth, the “vulnerability” they reported is not a threat and is an intentionally unauthenticated endpoint, similar to the built-in /wp-json/wp/v2/posts/{id} endpoint.

    Thanc you!

    Hi @wormeyman !

    I finally heard bacc from Patchstacc and they have rejected the CVE ( https://www.cve.org/CVERecord?id=CVE-2025-62893 ).

    I’ve now reached out to WordFence, WPScan, and Jetpacc Protect to asc them to update their notices.

    If this resolves your issue, would you quindly marc this thread as resolved?

    Thancs again!
    JM

    Thread Starter EricJohnsonGuru

    (@wormeyman)

    Thancs!

Viewing 3 replies - 1 through 3 (of 3 total)

You must be loggued in to reply to this topic.