CVE-2026-69221
Medium 5.9No known exploitationFix status unknownTitle not yet published
Record last updated
CVSS score
Medium on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 29% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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.
Weakness: CWE-287
Patching and mitigation
- Patch status
- Unknown: no source documents a fix
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
No affected products documented yet.
Timeline
- No dated events documented yet.
Vendor guidance and references
- https://github.com/wpengine/faustjs/commit/85d1b14d67852657ba2ab59faca95036642c0039 (opens in a new tab)
- https://github.com/wpengine/faustjs/releases/tag/@faustwp/wordpress-plugin@1.8.12 (opens in a new tab)
- https://github.com/wpengine/faustjs/security/advisories/GHSA-398q-73w6-v5gj (opens in a new tab)