Viewing 1 replies (of 1 total)
  • Yeah, it seems like there are some pretty minimal maintenance items that would really breathe some life back into this plugin (which the fact this plugin was updated a few months ago gives me some hope.)

    1. To your point on the security notice, admin settings are often overlooked for sanitization & output escaping since one might think the admins should be trusted with their own input on their own website, but sometimes admin users can be compromised and/or an intruder got access to update the setting via a different route somehow while these admin fields leave the possibility for it to then store/spread malicious code. Hopefully, this is a quick fix for the next release.

    – Not to hijack this topic, but there are also a few other items that are also hopefully quick updates to be made as well (consolidated things to maybe be more digestible in one place.) –

    2. I want to give a quick mention that https://github.com/stefangabos/Zebra_Tooltips shows a new version (2.3.0) was released a few months ago (January) while this plugin’s changelog doesn’t really mention having updated to use this new version. I think that should probably be grouped in since I don’t see why this would left as using an unpatched version of the tooltip library for any particular reason (meanwhile, this new version fixes a longstanding issue that this plugin will likely still have until it updates its copy of Zebra Tooltips.)

    3. https://www.ads-software.com/support/topic/php-warning-undefined-variable-selectors_string/ also seems like it should be a quick fix just to clean up the plugin’s PHP notices/warnings.

    4. Finally, it seems odd that this plugin was updated 3 months ago while it’s still saying it hasn’t been tested with the 3 latest major WordPress releases. This should be a simple matter of updating the “Tested up to” in the plugin’s info from being 5.0.18 to probably being 6.2, at this point.

    If it’s a bit much to keep making updates to this long-lived plugin, then it sure would be nice if this plugin were on GitHub (and is linked to from the plugin description & on its webpage so people then know about it.) These sorts of smaller updates would be perfect for people to just submit a quick pull request on so that the community of users can help make these fixes/improvements while it’s then just a matter of approving & releasing the new version.

Viewing 1 replies (of 1 total)
  • The topic ‘Security vulnerability <= version 2.1.4’ is closed to new replies.