---
id: "CVE-2026-69221"
page: "https://infrastack.ai/live/CVE-2026-69221"
kind: "vulnerability"
aliases: ["CVE-2026-69221"]
title: "Faust.js: FaustWP login skips WordPress MFA and SSO policies"
severity: "medium"
cvss: 5.9
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["faust.js", "faustwp", "headless-wordpress", "next.js", "package", "wordpress"]
not_affected_if: ["no-faustwp-local-login", "no-mfa-or-sso-policy", "version-1.8.12-or-later"]
published_at: "2026-11-16T20:19:10+00:00"
first_seen_at: "2026-11-16T20:38:46+00:00"
updated_at: "2026-11-16T20:39:37+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-69221", "first_seen_at": "2026-11-16T20:38:46+00:00"}]
exploit_sources: []
---

# Faust.js: FaustWP login skips WordPress MFA and SSO policies

Link for people: https://infrastack.ai/live/CVE-2026-69221 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed `@faustwp/core` version in `package.json` and lockfile; affected if below `1.8.12`.
- Check whether the WordPress site runs the FaustWP plugin with local login enabled and an MFA, SSO, or IP allowlist policy.
- Look for the `generateAuthorizationCode` mutation and `/api/faust/auth/token` endpoint in the deployment.

## Fix

- `@faustwp/core`: `1.8.12`

## Timeline

- 2026-11-16T20:38:46+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-69221

## Documents

- [advisory] Vendor advisory: github.com https://github.com/wpengine/faustjs/security/advisories/GHSA-398q-73w6-v5gj
- [fix] Patch: github.com https://github.com/wpengine/faustjs/commit/85d1b14d67852657ba2ab59faca95036642c0039
- [fix] Release notes: github.com https://github.com/wpengine/faustjs/releases/tag/@faustwp/wordpress-plugin@1.8.12

## From the sources

Faust.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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
