CVE-2026-69221: wpengine faustjs · Improper Authentication
Affects wpengine faustjsSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 1.8.12 when convenient.
Data as of 16 Nov 2026, 20:05 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.9 |
|---|
- Patch
- Available – fixed in 1.8.12
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade wpengine faustjs to 1.8.12.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| wpenginefaustjs | Affected
| Fixed in
|
AI-suggested
Upgrade Faust.js to version 1.8.12 or later, where this authentication bypass vulnerability is fixed. No other mitigation is required as the fix addresses the root cause.
Description
CVE-2026-69221 is an improper authentication vulnerability in wpengine's Faust.js toolkit for headless WordPress. Versions prior to 1.8.12 allow bypassing of WordPress authentication filters such as multifactor authentication, single sign-on, IP allowlists, or disabled account checks. This occurs because the generateAuthorizationCode GraphQL mutation calls authentication functions directly instead of the standard wp_authenticate filter. An attacker with valid credentials could obtain authorization codes and exchange them for access tokens even when normal login would deny access. The issue is fixed in version 1.8.12.