CVE-2026-69221 · Package
NO FIX YET · SEE WHAT TO DO
Faust.js's FaustWP plugin lets a user with valid WordPress credentials get an authorization code without passing multifactor, single sign-on, or IP allowlist checks. The attacker can exchange that code at the token endpoint for access and refresh tokens that the normal login would have denied.
first public Jul 6, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites that use FaustWP local login together with an authentication policy such as MFA, SSO, IP allowlists, or disabled accounts are exposed, because the flawed mutation bypasses those callbacks. Sites that use only the normal WordPress login, or no FaustWP local login, are not affected by this path.
Not affected if no-faustwp-local-login, no-mfa-or-sso-policy, version-1.8.12-or-later
Who cares faust.js, faustwp, headless-wordpress, next.js, wordpress
@faustwp/core version in package.json and lockfile; affected if below 1.8.12.generateAuthorizationCode mutation and /api/faust/auth/token endpoint in the deployment.@faustwp/core: 1.8.12Faust.js is a headless WordPress toolkit. Prior to 1.8.12, the FaustWP generateAuthorizationCode GraphQL mutation called wp_authenticate_username_password and wp_authenticate_email_password directly instead of using wp_authenticate. 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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.