sales@hackhalt.com

Home / Threats / CVE-2026-69221

WordPress component - Security Vulnerability (CVE-2026-69221)

CVE-2026-69221

Vulnerability CVE-2026-69221 MEDIUM

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-2026-69221

MEDIUM CVSS 5.9 Published 2026-11-16 Updated 2026-11-16
AI Risk Elevated (61/100) Active Exploit: No strong signal Published Exploit: Public exploit references found Priority: P3 Priority
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N
Affected Components 1
Reference Links 3
AI Risk Engine Elevated (61/100)
Exploitability Medium
Active Exploitation No strong signal
Published Exploit Status Public exploit references found

Threat Timeline

  1. 2026-11-16 CVE published and first recorded in the threat feed.
  2. 2026-11-16 Record updated with latest vulnerability metadata.
  3. 2026-11-17 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated just now

AI enriched just now (2026-11-17 17:47 UTC)

Technical Summary

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…

Potential Impact

Severity is MEDIUM (CVSS 5.9). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Medium based on published exploit references.

Primary risk drivers: published exploit references

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 61/100 (Elevated, Medium) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

WordPress component COMPONENT · unmapped Affected: < 1.8.12 Fixed in: 1.8.12

References

What to do about this

Patch on your next cycle Worth fixing, but not ahead of other work.

Fix it

Update WordPress component to 1.8.12 or later.

That is the complete fix. Everything below is what protects you in the meantime.

No Hack Halt control meaningfully contains this one — updating is the remedy. We would rather say so than sell you something that will not help.

Start free

Not sure if you are affected?

Scan your site to see whether it runs WordPress component, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs WordPress component. Versions below 1.8.12 are vulnerable; that release and later are not.

How do I fix it?

Update WordPress component to version 1.8.12 or later. That is the complete fix.