Needs better security features
Nathan Ingram’s old post (“What does this do?”) raises an important security concern. Old, insecure plugin versions remain in web-accessible folders with only a “security by obscurity” hope that the random folder names can’t be guessed. This may be an unlikely attack vector, but it’s just not good to keep obsolete and insecure code around a long time. A “delete old versions” feature — globally and per plugin — would be helpful. Even better: allow Plugversions to be limited in scope to individual, admin-selected plugins rather than every plugin. Edited: Thanks to Jose for explaining the stored plugin versions are not usable as exploitable code or payloads that could be activated by an attacker who did not already have the ability to install and activate anything they want. It’s still a danger to keep old, insecure code around, however — the likely mishap would come from user error where an old, insecure version is rolled back into use. Coupled with a good security monitoring plugin/service, Plugversions is a really helpful maintenance tool — and it would be more helpful if the old versions could be easily purged, identified if insecure, and not automatically stored for every plugin with every update. A simple per-plugin opt-in like “Enable Versioning” would prevent wasted storage space and retention of unwanted old code.
Dan Knauss
August 5, 2026
|
2 replies
FANTASTICO plugin
Plugin che fa esattamente quello che promette !!! Dovrebbe essere compreso di base nell’installazione di tutti i siti con wordpress !!!
This is a Must-Have!
PlugVersions is a WordPress game-changer, offering effortless plugin rollback for unmatched site stability and peace of mind. Essential, intuitive, and reliable, it’s more than a tool – it’s your website’s ultimate safety net.
Needs better security features
Nathan Ingram’s old post (“What does this do?”) raises an important security concern. Old, insecure plugin versions remain in web-accessible folders with only a “security by obscurity” hope that the random folder names can’t be guessed. This may be an unlikely attack vector, but it’s just not good to keep obsolete and insecure code around a long time. A “delete old versions” feature — globally and per plugin — would be helpful. Even better: allow Plugversions to be limited in scope to individual, admin-selected plugins rather than every plugin. Edited: Thanks to Jose for explaining the stored plugin versions are not usable as exploitable code or payloads that could be activated by an attacker who did not already have the ability to install and activate anything they want. It’s still a danger to keep old, insecure code around, however — the likely mishap would come from user error where an old, insecure version is rolled back into use. Coupled with a good security monitoring plugin/service, Plugversions is a really helpful maintenance tool — and it would be more helpful if the old versions could be easily purged, identified if insecure, and not automatically stored for every plugin with every update. A simple per-plugin opt-in like “Enable Versioning” would prevent wasted storage space and retention of unwanted old code.
Dan Knauss
August 5, 2026
|
2 replies
Not able to view any Revisions on plugin page.
This is useless plugin Simply creating and uploading a plugin on WordPress is not sufficient if it’s neither functioning correctly nor providing any option to display its intended features. Ensure that the plugin is properly coded, adheres to WordPress standards, and includes necessary hooks or settings for displaying its functionality. Debugging and testing are crucial before deploying it.
Graceful as it Is
Works excellently with Wordpress 6.4.3 and also with ClassicPress 2.0 (based on WP 6.3). Many thanks to good developer!
Not able to view any Revisions on plugin page.
This is useless plugin Simply creating and uploading a plugin on WordPress is not sufficient if it’s neither functioning correctly nor providing any option to display its intended features. Ensure that the plugin is properly coded, adheres to WordPress standards, and includes necessary hooks or settings for displaying its functionality. Debugging and testing are crucial before deploying it.
Graceful as it Is
Works excellently with Wordpress 6.4.3 and also with ClassicPress 2.0 (based on WP 6.3). Many thanks to good developer!
This is a Must-Have!
PlugVersions is a WordPress game-changer, offering effortless plugin rollback for unmatched site stability and peace of mind. Essential, intuitive, and reliable, it’s more than a tool – it’s your website’s ultimate safety net.
Disgraceful as it Is
Finally managed to delete this plugin by going to my host’s cpanel and deleting it from my file manager (as trying to delete it from my WordPress install gave a critical error message). The reason? I consider any rollback plugin as one that you can use, then delete it when you’ve done the rollback. This plugin though does not allow that and needs to be installed and live to go back to an older version. However, trying to delete it is where the fun starts: On deactivating PlugVersions, ALL of the versions of plugins, and themes that have been rolled back now appear as NEW plugins that need to be removed and deleted. These plugins also appear in WordFence – but when you see which plugins need updating, nothing is there – they just appear in your admin bar as plugins that need updating. I needed to delete 21 versions of plugins and themes and as already mentioned, delete Plugversions from my hosting cpanel. Probably the worst plugin that I’ve ever installed.
deeveearr
January 24, 2024
|
2 replies
Needs better security features
Nathan Ingram’s old post (“What does this do?”) raises an important security concern. Old, insecure plugin versions remain in web-accessible folders with only a “security by obscurity” hope that the random folder names can’t be guessed. This may be an unlikely attack vector, but it’s just not good to keep obsolete and insecure code around a long time. A “delete old versions” feature — globally and per plugin — would be helpful. Even better: allow Plugversions to be limited in scope to individual, admin-selected plugins rather than every plugin. Edited: Thanks to Jose for explaining the stored plugin versions are not usable as exploitable code or payloads that could be activated by an attacker who did not already have the ability to install and activate anything they want. It’s still a danger to keep old, insecure code around, however — the likely mishap would come from user error where an old, insecure version is rolled back into use. Coupled with a good security monitoring plugin/service, Plugversions is a really helpful maintenance tool — and it would be more helpful if the old versions could be easily purged, identified if insecure, and not automatically stored for every plugin with every update. A simple per-plugin opt-in like “Enable Versioning” would prevent wasted storage space and retention of unwanted old code.
Dan Knauss
August 5, 2026
|
2 replies
Not able to view any Revisions on plugin page.
This is useless plugin Simply creating and uploading a plugin on WordPress is not sufficient if it’s neither functioning correctly nor providing any option to display its intended features. Ensure that the plugin is properly coded, adheres to WordPress standards, and includes necessary hooks or settings for displaying its functionality. Debugging and testing are crucial before deploying it.
