stephankn

I have the same issue. After update it still complains about old version.

Best guess: The plugin checks only once in a while and waiting some time will fix it.

You could hide the warning for the time being.

Ok. I understand you use-case for it. Thank you for the explanation. How do I get rid of the listings after I pressed it? I would like to have only backups relevant to my current blog listed.

Basically I pressed it while trying to figure out why it did list 85 backups available with me having only 50 configured and my hosting storage space was close to be exhausted. As I couldn’t pinpoint this to a specific issue I thought the automatic cleanup was somehow out of sync.

Maybe a small confirmation window explaining what’s going to happen would have helped me avoiding to be surprised by the functionality. Given its use-case is quite limited, most people would not require it that often.

As the original question was answered I’ll marking this thread as resolved. Still would love to get hints on how to best clean up the backup listings so I don’t get confused by foreign backups.

Stephan

This is a serious issue. I recommend everyone to review the plugin configuration and change the Local folder path. Adding a longer random string at the end should do the trick.

The plugin author has to initialize the path on initialization with a not guessable value. Or even use a path which is not web-readable at all.

The logfile exposes existence of the vulnerability. Also consider censoring the exact path in the log output so users do not accidentally publish their site configuration.