Skip to main content
VulnerabilityPublished Updated

CVE-2026-56737: thorsten phpMyFAQ · Improper Authentication

Affects thorsten phpMyFAQSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 4.1.6 soon.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.1.6
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade phpMyFAQ and thorsten/phpMyFAQ to 4.1.6.

Affected software

ProductAffectedFixed in
thorstenphpMyFAQAffected
  • >=3.2.0 <4.1.6
Fixed in
  • 4.1.6
GitHubthorsten/phpMyFAQpkg:github/thorsten/phpMyFAQOther threatsAffected
  • >=3.2.0 <4.1.6
Fixed in
  • 4.1.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade affected phpMyFAQ installations to version 4.1.6 or later, which patches the vulnerability by requiring password authentication before TOTP verification and limiting failed TOTP attempts. No official workaround is documented.

Description

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.

References

Community reviews

Loading reviews…