Skip to main content
Menu
CVEs

CVE

Faust.js auth bypass in local login skips MFA and SSO

CVE-2026-69221

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N

5.9MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 1.8.12
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.8.12.

Published
Last modified
Reference
Last checked
24/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: no
  • Technical impact: partial

Summary

Faust.js, a headless WordPress toolkit, has a flaw in its FaustWP local login that lets an attacker with a valid username or email and password skip WordPress login policies, such as multifactor authentication, single sign-on, IP allowlists, and disabled-account checks, and obtain access and refresh tokens. The attacker can reach it remotely over the network with no user action, and the bypass works even when the normal WordPress login would be denied.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

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.

cve.now Index

24Pcve.now Index 24 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.9/10CVSS 5.9
  • No patch0/5No signal

What would change the score

  • Would score about 64 if added to CISA KEV
  • Would score about 59 if CISA's SSVC rates exploitation active
  • Would score about 43 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 1.8.12.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-69221 (FaustWP local login bypasses WordPress authenticate callbacks), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-69221 (entry last updated 2026-11-16):
Affected:
- wpengine faustjs: fixed in 1.8.12
Fixed versions: 1.8.12.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-69221 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-69221 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/wpengine/faustjs/security/advisories/GHSA-398q-73w6-v5gj
- https://github.com/wpengine/faustjs/commit/85d1b14d67852657ba2ab59faca95036642c0039
- https://github.com/wpengine/faustjs/releases/tag/@faustwp/wordpress-plugin@1.8.12
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-69221
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-69221"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • wpengine faustjs

    fixed in 1.8.12

Evidence 5

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Repository
  2. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-69221

Is CVE-2026-69221 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-69221?

faustjs: before 1.8.12.Source: cve.now feed data

How do I fix CVE-2026-69221?

Upgrade to a fixed version: 1.8.12.Source: cve.now feed data