Hi @sofiac1
When you use the link to see how the file has changed, what do you see?
Old file says: Tested up to: 4.9
Modified file says: Tested up to: 4.7.2
Filename: wp-content/plugins/so-css/readme.txt
File type: Plugin File
Plugin Name: SiteOrigin CSS
Plugin Version: 1.1.5
The Original Version of the file The Modified Version on your WordPress system
1 === SiteOrigin CSS === 1 === SiteOrigin CSS ===
2 Tags: css, design, edit, customize 2 Tags: css, design, edit, customize
3 Requires at least: 3.9 3 Requires at least: 3.9
4 Tested up to: 4.9 4 Tested up to: 4.7.2
5 Stable tag: 1.1.5 5 Stable tag: 1.1.5
6 Build time: 2017-09-19T17:05:02+02:00 6 Build time: 2017-09-19T17:05:02+02:00
7 License: GPLv2 or later 7 License: GPLv2 or later
Thanks. There isn’t anything in that change that could pose a security issue as far as I’m aware.
The current version has the following:
=== SiteOrigin CSS ===
Tags: css, design, edit, customize
Requires at least: 3.9
Tested up to: 4.9
So you’re welcome to delete SiteOrigin CSS, go to Plugins > Add New and reinstall it.
The core of your question though, pertains to a possible security issue from a changed file. To my knowledge a change in the tested version wouldn’t have any security implications.
Here is when the change was made: https://github.com/siteorigin/so-css/commit/8b35ee87c0460d264d0eaa439a6326e8c8843688.
Thanks.
If I delete your plugin and reinstall it, I imagine that any changes that I made with it would be lost. Is that correct? Or am I worrying about nothing?
Thanks for all your help!
Sofia
Your Custom CSS will be safe during an update process like that. You can delete the plugin and reinstall it 🙂