CVE-2026-111882: phpMyFAQ 3.2.0-alpha before 4.1.9 and 4.2.0-alpha before 4.2.0-beta TOTP 2FA Bypass via SSO Callbacks

Published Oct 17, 2026
·
Updated

phpMyFAQ 3.2.0-alpha before 4.1.9 and 4.2.0-alpha before 4.2.0-beta contains an authentication bypass vulnerability that allows IdP-authenticated users to skip TOTP two-factor authentication through the Keycloak and Entra ID SSO callbacks. Attackers holding a valid or phished IdP identity linked to a 2FA-enabled account can complete the OIDC flow and obtain a fully authenticated session, including administrator accounts.

Affected Software

1 affected component
PhpMyFaq phpmyfaq>=3.2.0-alpha<4.1.9, >=4.2.0-alpha<4.2.0-beta

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade phpMyFAQ to a version that resolves this vulnerability.

    Fixed in 4.1.9
  2. Upgrade

    Upgrade phpMyFAQ to a version that resolves this vulnerability.

    Fixed in 4.2.0-beta

Event History

Oct 17, 2026
CVE Published
via MITRE·06:46 PM
Data Sourced
via MITRE·06:46 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An attacker needs a valid or phished identity from the configured identity provider that is linked to a phpMyFAQ account with TOTP 2FA enabled. The affected SSO paths are the Keycloak and Entra ID callbacks, and administrator accounts are included.

2

Does exploitation require access to the phpMyFAQ account's TOTP code?

No. An attacker can complete the OIDC flow through the affected SSO callbacks and obtain a fully authenticated session without satisfying TOTP.

3

Which releases are affected?

Affected versions are phpMyFAQ 3.2.0-alpha before 4.1.9, and 4.2.0-alpha before 4.2.0-beta.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203