CVE-2026-69221: FaustWP local login bypasses WordPress authenticate callbacks

Published Nov 16, 2026
·
Updated

Faust.js is a headless WordPress toolkit. Prior to 1.8.12, the FaustWP generateAuthorizationCode GraphQL mutation called wpauthenticateusernamepassword and wpauthenticateemailpassword directly instead of using wpauthenticate. This bypassed callbacks registered on WordPress's outer authenticate filter, including policies for multifactor authentication, single sign-on, IP allowlists, or disabled accounts. On a site using FaustWP local login and one of those policies, an attacker with a valid username or email and password could obtain an authorization code and exchange it through /api/faust/auth/token for access and refresh tokens even when the normal WordPress login path would deny access. This issue is fixed in version 1.8.12.

Affected Software

1 affected component
WP Engine FaustWP<1.8.12

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.8.12

Event History

Nov 16, 2026
CVE Published
via MITRE·07:52 PM
Data Sourced
via MITRE·07:52 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this bypass?

Sites using FaustWP local login and a WordPress policy implemented through the outer authenticate filter are exposed before version 1.8.12. Relevant policies include multifactor authentication, single sign-on, IP allowlists, and disabled-account controls.

2

What does an attacker need to exploit it?

An attacker needs a valid WordPress username or email address and the corresponding password. They can use the FaustWP generateAuthorizationCode GraphQL mutation, then exchange the resulting authorization code through /api/faust/auth/token for access and refresh tokens.

3

Are sites that rely only on the normal WordPress login flow affected?

The described bypass applies to FaustWP local login through its GraphQL authorization-code flow. The normal WordPress login path can still deny the login under the configured authenticate-filter policy, while the affected FaustWP flow bypasses that policy.

4

What is the remediation?

Upgrade the FaustWP WordPress plugin to version 1.8.12, which fixes the issue. Until upgrading, treat FaustWP local-login token issuance as unable to enforce policies registered on WordPress's outer authenticate filter.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203