Skip to content
Fencer Vulns
high 8.1

CVE-2026-56737 json

phpMyFAQ's two-factor authentication login bypasses the password factor

published 2026-09-24 46 d ago modified 2026-09-29 41 d ago also EUVD-2026-85931 , GHSA-8gpw-xvpf-hvx5

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

Summary

phpMyFAQ is an open source FAQ web application. Versions 3.2.0 through 4.1.5 contain an authentication bypass in its public two-factor authentication verification flow: an unauthenticated attacker can submit an account’s numeric user ID and a valid or brute-forced six-digit TOTP code without first authenticating with the account password, allowing takeover of any 2FA-enabled account, including administrator accounts. Version 4.1.6 is patched by binding TOTP verification to a session established after successful password authentication and limiting failed TOTP attempts. No official workaround is documented; affected installations should upgrade to 4.1.6 or later.

Patch / fix

  • packagist thorsten/phpmyfaq 4.1.6
  • packagist phpmyfaq/phpmyfaq 4.1.6
  • phpmyfaq phpmyfaq 4.1.6

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
41 d ago

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-8gpw-xvpf-hvx5 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist thorsten/phpmyfaq
>=3.2.0, <4.1.6
4.1.6
packagist phpmyfaq/phpmyfaq
>=3.2.0, <4.1.6
4.1.6

Affected products

  • thorsten phpMyFAQ

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.