Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    A blue acrylic keychain spelling KEYS lies on a grey surface with a metal key ring and two keys beside it.
    Photo by Franck / Unsplash

    phpMyFAQ 4.1.12 fixes reset flaw letting Keycloak and other SSO accounts skip MFA

    A medium-severity flaw in phpMyFAQ password reset lets someone with mailbox access set local passwords on SSO-managed accounts. Update to 4.1.12 or 4.2.0-RC.2.

    phpMyFAQ password reset lets SSO accounts get local passwords

    phpMyFAQ has an authentication bypass in its password reset function, tracked as CVE-2026-130347. Accounts that sign in through an external identity provider can be given a local password, which sidesteps the provider's multi-factor authentication and deprovisioning. The CVSS 4.0 score is 6.3, rated medium.

    How a mailbox turns into a local login

    An attacker with access to the account's mailbox requests a password reset token for an externally authenticated account, sets a local password, and logs in locally. The affected account types include OIDC, Keycloak, Entra ID, LDAP, SSO and WebAuthn. The CVSS vector lists a network attack vector and high attack complexity, with no privileges or user interaction required.

    phpMyFAQ before 4.1.12 and 4.2.0 alphas are affected

    The flaw affects phpMyFAQ before 4.1.12 and 4.2.0-alpha builds before 4.2.0-RC.2. You are most exposed if you use phpMyFAQ with an external identity provider and rely on it for MFA or for cutting off departed users. Keycloak is only one of the identity-provider setups involved; the flaw is in phpMyFAQ, not in Keycloak. The sources do not say whether the flaw is being exploited.

    Update to phpMyFAQ 4.1.12 or 4.2.0-RC.2

    Upgrade to 4.1.12 on the stable branch, or to 4.2.0-RC.2 if you run the 4.2 pre-releases. These fixed versions are inferred from the affected ranges and the release tags the record references, not stated outright. No workaround is stated, so updating is the available fix. The record points to GitHub advisory GHSA-59x6-g992-q3fm and fix commit 631c0765ee14a591a2bdafeacb1346bd03b27ea3.

    What the CVE record leaves open

    The NVD labels the record status "Deferred", and no disclosure or patch dates are given.

    Product Affected Fixed
    phpMyFAQ 4.1.x before 4.1.12 4.1.12
    phpMyFAQ 4.2.0 pre-releases 4.2.0-alpha before 4.2.0-RC.2 4.2.0-RC.2

    Sources

    Image: Photo by Anna Khromova on Unsplash


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion