Skip to main content
VulnerabilityPublished

CVE-2026-69221: wpengine faustjs · Improper Authentication

Affects wpengine faustjsSource CVE Database V5

0
Compare

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

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
wpenginefaustjsAffected
  • <1.8.12
Fixed in
  • 1.8.12

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.

References

Community reviews

Loading reviews…