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.
Published: 2026-10-17
Score: 7.7 High
EPSS: < 1% Very Low
KEV: No
Impact: Account takeover via Keycloak implicit linking
Action: Immediate Patch
AI Analysis

Impact

phpMyFAQ versions 4.2.0‑alpha up to before 4.2.0‑beta allow an attacker to bypass authentication by exploiting the Keycloak integration. The flaw lets a Keycloak user with a colliding preferred_username or unverified email bind their Keycloak subject to a local account through the /auth/keycloak/authorize endpoint, resulting in superadmin privileges for the attacker. This can compromise the entire system and any data managed by phpMyFAQ.

Affected Systems

The affected product is phpMyFAQ, developed by thorsten, a web‑based FAQ management system. The vulnerability exists in releases 4.2.0‑alpha through just before 4.2.0‑beta; all earlier 4.1.x or 4.0.x versions are unaffected. Users running the vulnerable releases should verify their installed version against the vendor’s release notes.

Risk and Exploitability

The CVSS score of 7.7 indicates a high severity. Because EPSS data is unavailable, the exact likelihood of exploitation cannot be quantified, but the vulnerability is not listed in the CISA KEV catalog. An attacker must control a Keycloak identity that matches a local preferred_username or uses an unverified email. Once they craft a request to /auth/keycloak/authorize, the system automatically links the identities, causing an authentication bypass and privilege escalation.

Generated by OpenCVE AI on October 17, 2026 at 21:23 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade phpMyFAQ to a patched release (4.2.0‑beta or newer).
  • Temporarily disable or remove the Keycloak integration to stop automatic account linking until the patch is applied.
  • Revoke or delete any local accounts linked to suspicious Keycloak IDs and enforce strict username or email uniqueness in Keycloak to prevent accidental linking.

Generated by OpenCVE AI on October 17, 2026 at 21:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 18 Oct 2026 12:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Sat, 17 Oct 2026 19:00:00 +0000

Type Values Removed Values Added
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.
Title phpMyFAQ 4.2.0-alpha before 4.2.0-beta Account Takeover via Keycloak Implicit Account Linking
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
Weaknesses CWE-287
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 7.7, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}


Subscriptions

Phpmyfaq Phpmyfaq
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-10-18T11:21:21.852Z

Reserved: 2026-10-17T12:16:44.850Z

Link: CVE-2026-111898

cve-icon Vulnrichment

Updated: 2026-10-18T11:21:18.531Z

cve-icon NVD

Status : Deferred

Published: 2026-10-17T19:16:31.647

Modified: 2026-10-18T12:17:10.383

Link: CVE-2026-111898

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-17T21:30:06Z

Weaknesses