SS Reporting Issues with Removed Plugins

  • Resolved rjbinney

    (@rjbinney)


    1 year, 11 months ago

    I routinely get three error messages in my reports:

    1. WordPress Jetpack plugin <= 13.3.1 – Authenticated (Contributor+) Stored Cross-Site Scripting via wpvideo Shortcode vulnerability
    2. WordPress WP Reset PRO Premium Plugin <= 5.98 – Cross-Site Request Forgery (CSRF) vulnerability leading to Database Reset
    3. WordPress WP Reset PRO Premium Plugin <= 5.98 – Authenticated Database Reset vulnerability

    As to 2) and 3): I installed WP Reset plugin (never upgraded to a premium version) but removed it even before installing Solid Security. (Removed, not made inactive. As far as I can tell, she gone.)

    As to 1): I got no idea what that means. I have no videos on my site so I don’t know if I should worry. I would presume JetPack is enough of a legit presence in the WP system that it wouldn’t have any major lasting flaws?

    Anyway, how the heck do I get rid of the WP Reset errors – when I don’t even have that plugin anymore?!?

    The page I need help with: [log in to see the link]

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

    (@macmanx)

    1 year, 11 months ago

    Item 1 is easy, it’s reporting a security issue in Jetpack 13.3.1 and older. Jetpack’s current version is 13.5. So, to fix the security issue, and remove the error message, simply update Jetpack.

    I can’t speak for items 2 and 3, because they’re premium plugins, so I have no access to them without buying them myself, but I suspect they are also out of date on your site.

    Thread Starter rjbinney

    (@rjbinney)

    1 year, 11 months ago

    I’m running Jetpack 13.5.

    And I don’t have WP Reset Pro installed.

    Plugin Support chandelierrr

    (@shanedelierrr)

    1 year, 11 months ago

    Hi @rjbinne, glad you reached out!

    When you keep receiving Site Scan reports of already-updated or removed plugins/themes, it could be due to either of the following:
    (1) the notification is coming from a different site (most likely an old staging site that’s still up somewhere)
    (2) OR you’re receiving outdated scan emails that got stuck in the server

    Can you please check with your existing (or old host) if you have a staging site somewhere with the Solid Security plugin still installed and activated? Please note that even if the old site isn’t accessible, but the cron is still running, it will still be trying to run the site scan.

    To investigate further, go to your live site’s Security > Logs page, click “Screen Options” at the top-right, and check both the “Show Debug entries” and “Show Process entries” boxes (see here), then apply the changes to load more logs. 

    Next, filter the Notification Center module and view the details of the most recent “Sending site scan results” entry (see here) to know if the email you received was triggered from the site. If you can send a screenshot of what you see, that would help (blur the info you prefer not to share).

    If you’ve confirmed that there is no staging/other site and the email was not triggered from your live site, I’d recommend checking the email logs/server to investigate if you’re receiving notifications that got stuck there.

    Let us know what you can find!

    Plugin Support chandelierrr

    (@shanedelierrr)

    1 year, 10 months ago

    Hi there,

    I hope the previous reply was helpful. Due to inactivity, I’ll be closing this post.

    If you still need some assistance, feel free to reply back or open a new support ticket, and we’d be happy to assist. 

    Thank you!

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

The topic ‘SS Reporting Issues with Removed Plugins’ is closed to new replies.

Tags