Suspicious folders at /wp-content/cache/supercache folder

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

  • In short, the client (bot or whatever) is supplying a fake host header causing WPSuperCache to write a new folder.
    A simple fix would be to check the HTTP_HOST variable against a valid list of hosts in your .htaccess file.

    You can see a proof of concept here: https://youtu.be/CkYUFr86bCA

    Hello,

    I had the same issue and my host told me it was because of SNI. Any website without SSL certificate hosted on the same server as you might show up in your cache when accessed via https. I don’t have the issue any more, no idea what solved it.

    Cheers

    Thread Starter Dmitry Motorin

    (@dmitry-motorin)

    Roger Elve,
    Thank you. I’ll try

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Suspicious folders at /wp-content/cache/supercache folder’ is closed to new replies.