CVE-2026-130347 in phpMyFAQ
Summary
by MITRE • 11/17/2026
phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authentication bypass in password reset, letting external-identity accounts receive local passwords. Attackers with mailbox access can request reset tokens for OIDC, Keycloak, Entra ID, LDAP, SSO, or WebAuthn accounts and log in locally, skipping IdP MFA and deprovisioning.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 11/17/2026
The vulnerability identified in phpMyFAQ versions prior to 4.1.12 and the pre-release version 4.2.0-RC.2 represents a critical authentication bypass mechanism rooted in flawed identity management logic during the password reset workflow. This flaw specifically targets external identity accounts, which are typically managed through third-party Identity Providers such as OpenID Connect providers like Keycloak or Entra ID, Lightweight Directory Access Protocol servers for LDAP integration, Single Sign-On systems, and WebAuthn implementations. The core technical deficiency lies in how the application handles credential updates for users who do not possess a local password hash by default. When an administrator or system process assigns a new local password to such an account, the software fails to properly segregate this action from standard authentication flows, effectively allowing these externally authenticated accounts to be accessed via traditional username and password credentials rather than solely through their designated identity provider.
From a technical perspective, the exploitation of this vulnerability requires minimal prerequisites for the attacker but yields significant security implications. An adversary who has gained access to an email mailbox associated with any user account within the phpMyFAQ instance can initiate a password reset request regardless of whether that account is configured as local or external. The system generates and delivers a reset token via email, which, when utilized, allows the setting of a new local password for the target account. Once this local credential pair is established, the attacker can authenticate directly against the application using standard HTTP authentication mechanisms. This process effectively bypasses any multi-factor authentication policies enforced by the external identity provider because the application accepts the newly created local credentials as valid without requiring re-verification through the IdP.
The operational impact of this vulnerability extends beyond simple unauthorized access to a complete circumvention of security controls designed for federated identities. By logging in locally, attackers can bypass Multi-Factor Authentication requirements that are typically enforced at the identity provider level during OIDC or SSO flows. Furthermore, because the attacker now possesses valid local credentials, they may be able to manipulate account states, potentially leading to unauthorized deprovisioning of accounts or modification of user roles and permissions within the application. This undermines the principle of least privilege and can lead to broader system compromise if the affected phpMyFAQ instance has integrations with other backend services or databases where elevated privileges are granted based on local role assignments rather than federated identity claims.
This vulnerability aligns closely with CWE-287, which describes Improper Authentication, specifically regarding failures in verifying credentials for accounts that utilize external authentication sources. It also relates to CWE-640, Weak Password Recovery Mechanism for Forgotten Password, as the reset process does not adequately distinguish between local and federated account types when allowing password changes. In terms of MITRE ATT&CK framework mapping, this behavior facilitates Account Manipulation (T1098) by enabling attackers to establish persistent access through locally managed credentials that bypass identity provider controls, and potentially Credential Access (T1078) if the local passwords are reused or can be cracked offline after extraction.
Mitigation strategies must prioritize immediate patching of phpMyFAQ to version 4.1.12 or later, where this logic flaw has been addressed by ensuring that password reset operations for external identity accounts either prevent the creation of local credentials entirely or enforce re-authentication through the original identity provider upon any credential change. Administrators should also implement strict email security controls and monitor for unusual password reset requests associated with federated accounts. Additionally, enforcing multi-factor authentication at the application level rather than relying solely on the identity provider can provide a secondary layer of defense, although patching remains the primary corrective action to eliminate this specific bypass vector.