WordPress 7.2 drops its new Secrets API days before release
A security review found the capability checks guarding the feature were never implemented, so WordPress pulled it from 7.2 just before release, targeting 7.3 instead.
WordPress has pulled its new Secrets API from the 7.2 release, days before the planned 8 December ship date. A note added to the Secrets API dev post on 17 November says simply: “The Secrets API will no longer be shipping with WordPress 7.2. See r65538.”
The reversal follows a security review. Core contributor Peter Wilson found that the capability checks meant to gate the feature, manage_secrets and manage_network_secrets, were introduced in the initial commit but never actually enforced in the code. Separately, Ryan McCue raised an architectural objection: the API mixed two different ideas, platform-provided secrets and application-managed encrypted data, without a clear line between them. Eric Mann says he wants to bring the feature back for 7.3 “if possible.”
If you had started adapting a plugin to use wp_set_secret() and wp_get_secret() after the 15 November announcement, that work now has nowhere to land in 7.2. The API encrypted credentials at rest instead of leaving them as plaintext in wp_options, which is still a real gap worth solving, just not solved yet.
Why it matters: a headline security feature for plugin developers got pulled for failing its own security review, five weeks after being announced. Treat anything you build against the Secrets API as unstable until it reappears, with working capability checks, in a future release.