Live › vulnerability › CVE-2026-111898
Go to dashboardphpMyFAQ 4.2.0-alpha before 4.2.0-beta matches Keycloak logins to existing local accounts by preferred_username or email without proper verification. An attacker who controls a Keycloak identity with a colliding username or unverified email can log in through /auth/keycloak/authorize and gain superadmin privileges.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only instances running phpMyFAQ 4.2.0-alpha before 4.2.0-beta that have the Keycloak single sign-on integration enabled are exposed. Instances that use local logins only, or run a later release, can skip it.
No product ranges from the sources yet.
4.2.0-beta./auth/keycloak/authorize route in the web server logs.4.2.0-beta or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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 preferred_username 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.
This page as .md · .json · in your agent: get_signal("CVE-2026-111898")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.