CVE-2026-111898: phpMyFAQ 4.2.0-alpha before 4.2.0-beta Account Takeover via Keycloak Implicit Account Linking

Published Oct 17, 2026
·
Updated

phpMyFAQ 4.2.0-alpha before 4.2.0-beta contains an authentication bypass vulnerability that allows Keycloak users to take over local accounts by matching preferredusername or email. Attackers controlling a Keycloak identity with a colliding username or unverified email can log in through /auth/keycloak/authorize to bind their subject and gain superadmin privileges.

Affected Software

1 affected component
PhpMyFaq phpmyfaq>=4.2.0-alpha<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

Which deployments are exposed?

phpMyFAQ installations running 4.2.0-alpha before 4.2.0-beta that use Keycloak authentication are exposed through the /auth/keycloak/authorize flow.

2

What does an attacker need to exploit this?

The attacker needs control of a Keycloak identity whose preferred_username collides with a local account username, or whose email matches a local account email without being verified.

3

What is the resulting access level?

Successful exploitation binds the attacker's Keycloak subject to the matching local account and can grant superadmin privileges.

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