Is there a security vulnerability in Advanced Custom Fields related to the SCF fork?

It’s probably the issue mentioned in the changelog for 6.3.8 here. The developers were unable to release the patch on dot org themselves because Mullenweg had unilaterally revoked their access to the plugin repository because the plugin is owned by WP Engine. The issue has been patched in the version available directly from the developer, as you can see from the changelog.

The security issue used to justify the takeover of the plugin page only existed at that time because the developers were prevented from patching it themselves by the person who took it over. You can draw your own conclusions about what’s going on there.

tech