CVE-2026-111898

7.5High

Published 17 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

7.5High

Attack vector: Network
Complexity: High
Privileges needed: Low
User interaction: None
Impact: Full C/I/A compromise
Weakness: CWE-287

Impact

Authenticated Keycloak users can hijack local superadmin accounts and take over the phpMyFAQ instance. The attacker needs an existing Keycloak account with an email or username matching a local user.

Root cause

The application implicitly links Keycloak identities to existing local accounts solely by matching the preferred_username or unverified email claims.

Affected systems

phpMyFAQ 4.2.0-alpha before 4.2.0-beta

CVSS v3.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Fix & remediation

Upgrade phpMyFAQ to version 4.2.0-beta or later. As an interim workaround, disable Keycloak authentication or block access to /auth/keycloak/authorize.

shell

$ composer update phpmyfaq/phpmyfaq

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-111898