Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-111898 Overview
CVE-2026-111898 is an authentication bypass vulnerability in phpMyFAQ versions 4.2.0-alpha before 4.2.0-beta. The flaw allows attackers controlling a Keycloak identity to take over local phpMyFAQ accounts through implicit account linking. The Keycloak integration binds federated identities to local accounts by matching the preferred_username claim or email address. An attacker who registers a Keycloak user with a colliding username or an unverified matching email can authenticate through /auth/keycloak/authorize and inherit the privileges of the targeted local account, including superadmin roles. The vulnerability is tracked under [CWE-287: Improper Authentication].
Critical Impact
Attackers can hijack phpMyFAQ superadmin accounts by registering a Keycloak identity with a matching username or email, resulting in full administrative compromise of the FAQ platform.
Affected Products
- phpMyFAQ 4.2.0-alpha
- phpMyFAQ versions prior to 4.2.0-beta
- Deployments using the Keycloak identity provider integration
Discovery Timeline
- 2026-10-17 - CVE-2026-111898 published to NVD
- 2026-10-18 - Last updated in NVD database
Technical Details for CVE-2026-111898
Vulnerability Analysis
The vulnerability resides in the Keycloak OpenID Connect authorization flow exposed at /auth/keycloak/authorize. When a Keycloak-authenticated user reaches the callback, phpMyFAQ attempts to associate the external subject identifier with an existing local account. The association logic uses the preferred_username claim or the email address as the lookup key rather than requiring an explicit, pre-established binding.
Because phpMyFAQ does not verify that the matched local account was previously linked to that Keycloak subject, the first login from a colliding identity causes the subject to be bound to the local account. Subsequent authentications succeed under that identity. If the matched local account is a superadmin, the attacker inherits full administrative control over the phpMyFAQ instance.
Root Cause
The root cause is improper authentication logic in the federated identity linking workflow. The implementation trusts user-controlled OpenID Connect claims (preferred_username and email) as sufficient proof of identity ownership, without validating email verification status or requiring an administrator-approved link. This pattern falls under [CWE-287] and specifically reflects an insecure implicit account-linking design.
Attack Vector
An attacker provisions an account in a Keycloak realm that the vulnerable phpMyFAQ instance trusts. They set preferred_username to match a target phpMyFAQ user, or register an unverified email that collides with a target local account. The attacker then initiates the OIDC login flow via /auth/keycloak/authorize. On successful callback, phpMyFAQ binds the attacker's Keycloak subject to the collided local account and issues a session with that account's privileges.
Verified public exploit code is not available at the time of writing. See the GitHub Security Advisory and the VulnCheck Advisory for phpMyFAQ for additional technical context.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-111898
Indicators of Compromise
- Successful authentications to /auth/keycloak/authorize followed immediately by administrative actions in phpMyFAQ.
- New Keycloak subject identifiers (sub claim) bound to pre-existing local accounts, especially superadmin accounts.
- Keycloak login events for users with unverified email addresses that match registered phpMyFAQ accounts.
Detection Strategies
- Audit the phpMyFAQ user table for any local account whose associated Keycloak subject changed after upgrading to or deploying 4.2.0-alpha.
- Correlate Keycloak authentication logs with phpMyFAQ session creation and privilege-sensitive actions such as user management or configuration changes.
- Alert on first-time Keycloak logins that resolve to high-privilege local accounts.
Monitoring Recommendations
- Enable verbose logging on the phpMyFAQ Keycloak authentication handler to capture claim values used for account resolution.
- Monitor Keycloak admin events for creation of users whose preferred_username or email matches existing phpMyFAQ identities.
- Track and alert on changes to superadmin role assignments within phpMyFAQ.
How to Mitigate CVE-2026-111898
Immediate Actions Required
- Upgrade phpMyFAQ to 4.2.0-beta or later, where implicit account linking is removed.
- Temporarily disable the Keycloak authentication provider if an upgrade cannot be applied immediately.
- Review all local superadmin accounts and reset any Keycloak subject bindings that cannot be verified as legitimate.
Patch Information
The vulnerability is fixed in phpMyFAQ 4.2.0-beta. The maintainers' advisory is published at GHSA-rg4w-2j3r-2hhp. Administrators should apply the upgrade and audit historical authentication events for any suspicious bindings that may have occurred prior to patching.
Workarounds
- Restrict the trusted Keycloak realm to internally provisioned users only, and disable self-service registration.
- Enforce verified-email requirements in Keycloak so unverified addresses cannot be used to assert identity.
- Remove any pre-existing local phpMyFAQ accounts that are intended to be managed exclusively through federated identity, eliminating collision targets.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

