Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator James Huff

    (@macmanx)

    @benixgo It looks like Sucuri is reading this plugin’s integration files as if they were the actual plugins they’re named after.

    Taking this one for example:

    vulnerable Jetpack plugin found at ./wp-content/plugins/gamipress/integrations/jetpack/jetpack.php – Version: 1.0.0 Please update this plugin immediately: https://jetpack.com/blog/jetpack-12-1-1-critical-security-update/

    If you were indeed using Jetpack 1.0.0 that would indeed be very bad. As the link mentions, there is a security vulnerability with Jetpack 12.1.1 and lower.

    But, you don’t have to worry. The current version of Jetpack is 13.9, has no known vulnerabilities, and the file in question is just version 1.0.0 of GamiPress’s Jetpack integration, which is, crucially, not the Jetpack plugin.

    @gamipress You might want to consider renaming those files, so something like this doesn’t happen.

    Plugin Author Ruben Garcia

    (@rubengc)

    Hi @macmanx

    I’m Ruben, CEO at GamiPress & AutomatorWP

    We do not know why Sucuri stills working with those files since they are not in the main directory where the plugin file should be placed

    We reported it several times to Sucuri to do not check files in subfolders as the main one, other security plugins already fixed it but seems that Sucuri is still working on this fix yet…

    Moderator James Huff

    (@macmanx)

    These security scanners are blunt instruments, they can only be as smart as their developers make them.

    I can guess why Sucuri thought that /wp-content/plugins/gamipress/integrations/jetpack/jetpack.php was /wp-content/plugins/jetpack/jetpack.php

    It’s annoying, it should be fixed on Sucuri’s end, but it is plausible.

    I think the only effective way forward, or at least the only way forward in your control, is to rename the files themselves, like /integrations/jetpack/jetpack.php to /integrations/jetpack/gamipress-jetpack.php

    I know that’s a fair bit of work, but the confusion amongst your existing and future users will continue until either you do that or Sucuri finally fixes their scanner, and you can only control your own stuff.

    Thread Starter Benixgo

    (@benixgo)

    Ok that’s what I thought, thanks for the quick answers guys, I will also open a ticket with Sucuri, hope that helps!

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