# phpMyFAQ's two-factor authentication login bypasses the password factor Advisory record · `GHSA-8gpw-xvpf-hvx5` - **Identifiers:** `GHSA-8gpw-xvpf-hvx5` · `CVE-2026-56737` · `PKSA-p9tj-4psw-jkcc` · `PKSA-tcxy-t63n-k6vh` - **State:** Confirmed - **Severity:** CVSS 8.1 High - **Critical:** No - **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html) - **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) - **Published:** 24 Sept 2026 - **Updated:** 24 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 24 Sept 2026, 19:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `thorsten/phpmyfaq` (Packagist): affected `>=3.2.0, <4.1.6`; fixed in `4.1.6` - `phpmyfaq/phpmyfaq` (Packagist): affected `>=3.2.0, <4.1.6`; fixed in `4.1.6` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Packages phpmyfaq/phpmyfaq and thorsten/phpmyfaq, versions 3.2.0 up to but not including 4.1.6, have an authentication bypass in the frontend two-factor login. The public verification endpoint logs a user in using only a valid 6-digit TOTP code and a user ID, without requiring the password to have been checked first, so an unauthenticated attacker who can reach the endpoint could sign in to any account with 2FA enabled, including administrator accounts, and the code can be guessed because the endpoint has no lockout. Upgrade to version 4.1.6, which is the listed fixed version. Written 31 Oct 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 8.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0053, the 45th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 13:54 UTC: First seen by agentprime - 31 Oct 2026, 13:54 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-8gpw-xvpf-hvx5) ## Sources - [GitHub Advisory Database: GHSA-8gpw-xvpf-hvx5](https://github.com/advisories/GHSA-8gpw-xvpf-hvx5) - [OSV: GHSA-8gpw-xvpf-hvx5](https://osv.dev/vulnerability/GHSA-8gpw-xvpf-hvx5) - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .