Re:WordPress.org's latest move involves taking control of a ...
by maxloh on Sunday October 13, 2024 @05:41AM
(#41826530)
WP Engine fixed the vulnerability about a week ago [0].
The WP security team may have just backported the fix, even using the same line in their changelog [1].
[0]: https://www.advancedcustomfields.com/changelog/
[1]: https://plugins.trac.wordpress.org/changeset?new=3164480%40a...
I'm guessing the WP security team has been pentesting any WPEngine code they could get their hands on to find an excuse to make all of these changes. The security issues do look bad (once again proving that WordPress' worst vulnerabilities come from the plugins they install) but I think the branding removal is pretty wild.
A quick skim through the plugin development guidelines does seem to indicate that trialware isn't allowed, and the plugin seems to be doing all kinds of other stuff that isn't really permitted by the guidelines. I don't know if WordPress is as strict in enforcing those as they are with this plugin, but the changes do seem to be based on them.
With WPEngine recommending people to install their (vulnerable) version, I once again feel like there's no right side in this conflict. What a mess.