Comment on
Moin,
Comment on
Moin,
Comment on
Who could foresee that a plugin would get pulled from the WordPress plugin directory for a security issue when the developer has left in commented out security checks?
Reply in thread
This is the plugin: https://wordpress.org/plugins/sendpress/ These are security changes the developer made today, which presumably is in response to the plugin being closed for a security issue: https://plugins.trac.wordpress.org/changeset/2990357/ Here is the file from the screenshot: https://plugins.trac.wordpress.org/browser/sendpress/trunk/classes/views/class-sendpress-view-pro.php?rev=2990358 The code in that file is still missing needed security even after the security change made today.
Comment on
3 WordPress Firewall Plugins Stop Recent Widely Exploit Vulnerability in tagDiv Composer Plugin
Comment on
WordPress 6.3.2 – Maintenance and Security release
Comment on
Hacker Likely Targeting This Incompletely Fixed Authenticated Plugin Installation Vulnerability in WordPress Plugin NextMove Lite
Other data providers including Patchstack, Wordfence, and WPScan are all listing the vulnerability as having been fixed, despite the developer only partially fixing it.
Comment on
Wordfence's False Claim of Vulnerability in WordPress Plugin Everest Backup Leads to Serious Real Vulnerability
Reply in thread
Comment on
Wordfence's False Claim of Vulnerability in WordPress Plugin Everest Backup Leads to Serious Real Vulnerability
Reply in thread
Comment on
Wordfence Security's Country Blocking Isn't an Effective Measure Against Hackers
Reply in thread
Even better is to use tools that provide effective protection, as multiple tools that don't provide effective protection are still unlikely to provide effective protection when combined.
Comment on
Wordfence's False Claim of Vulnerability in WordPress Plugin Everest Backup Leads to Serious Real Vulnerability
Reply in thread
Again with the projection. You are the only one ranting here. We don't have any "scammy-ass" plugins.
The post you are replying about mentioned Wordfence in the context of us explaining how we came across a serious vulnerability. Which involved us reviewing a false claim by Wordfence about a vulnerability in a plugin one of our customers started using. So it wasn't altruistic, our customers pay us to do that work. We mentioned WordPress in the context of boilerplate text explaining why we full disclosed the vulnerability. None of that is a rant.
You can't even keep your claims straight. First you claimed we hadn't explained what the moderators we doing that is inappropriate and then you claimed we had, but you don't agree with it. To quote you, "No one is going to trust you or listen to you if you can’t be honest about what’s happening."
Comment on
Wordfence's False Claim of Vulnerability in WordPress Plugin Everest Backup Leads to Serious Real Vulnerability
Reply in thread
Comment on
Wordfence's False Claim of Vulnerability in WordPress Plugin Everest Backup Leads to Serious Real Vulnerability
Reply in thread
You seem to have us confused with someone else. We haven't claimed that WordPress forum moderators are out to get us or and we don't have a victim complex. Perhaps you have an issue with projection. The moderators do act inappropriately, which plenty of people in the WordPress community have dealt with. It is why so few people participate in them.
As for what the moderator are doing inappropriately, we explained some of that here. That was linked to in the post you are replying about. It would help to read what you responding before claiming it doesn't provide something. And here is specific example, which had nothing to do with us, where they deleted messages simply saying thank you.