Skip to content
CVE-2026-129056: update the WordPress Authorizer plugin

CVE-2026-129056: update the WordPress Authorizer plugin

November 21, 2026

Patchstack’s CNA record for CVE-2026-129056 rates the issue Critical, with a CVSS 3.1 score of 9.8. It records public disclosure on November 18, 2026, followed by publication of the CVE record on November 20.

Install the corrected plugin

Authorizer versions before 3.17.2 are affected. The CNA explicitly recommends the latest available version, at least 3.17.2. The official WordPress listing offers 3.17.2 at this writing.

Confirm that the installed package is authorizer, published by Paul Ryan. Record its version for each WordPress installation and any shared multisite deployment. Updating WordPress core or the external identity provider alone does not replace this plugin.

Before maintenance, preserve a recoverable backup of site files and the database. Record the intended access policy and the configured identity provider so that ordinary sign-in can be checked after the update. Keep a documented administrative recovery procedure available to the operator.

The 3.17.2 changelog warns that some OIDC/OAuth2 configurations will require manual email verification. Confirm that WordPress can send email before upgrading, using a mailbox controlled by the operator, and include that verification step in the post-update sign-in check where applicable.

Check the selected plugin release’s compatibility requirements, then update through WordPress or the site’s established deployment process. For a vendor-maintained package with a backported correction, retain that vendor’s explicit CVE status and exact package build instead of relying only on the upstream version label.

Verify access after the update

Confirm the installed plugin version on every serving copy. In a multisite setup, have the network administrator verify the shared plugin code and which sites use it.

Using approved test accounts, complete the site’s ordinary sign-in flow with its configured provider and confirm that the resulting access matches the intended policy. Review the configured approved-user list and site visibility settings against the pre-maintenance record. These are normal administrative checks, not attempts to reproduce the vulnerability.

Retain the update result and corrected version with the verification record. A working login confirms operation, but does not by itself prove that all application servers received the corrected plugin.

Acknowledgements

This post was created with assistance from AI.

Last updated on