Skip to main content
VulnerabilityPublished Updated

CVE-2026-76214: thorsten phpMyFAQ · Authentication Bypass by Capture-replay

Affects thorsten phpMyFAQSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.1.7 as a priority.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.1.7
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 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 16 Nov 2026.

What to do

Upgrade thorsten phpMyFAQ to 4.1.7.

Affected software

ProductAffectedFixed in
thorstenphpMyFAQAffected
  • <4.1.7
Fixed in
  • 4.1.7
GitHubthorsten/phpMyFAQpkg:github/thorsten/phpMyFAQOther threatsAffected
  • <=4.1.5
Fixed in–

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

AI-suggested

Patch to phpMyFAQ version 4.1.7 or later where this issue is fixed. Since no vendor advisory or patch link is provided, verify with the official phpMyFAQ project for the availability of the fix. Until patched, consider disabling WebAuthn login or implementing additional controls to prevent replay attacks.

Description

phpMyFAQ versions before 4.1.7 have an authentication bypass vulnerability due to failure to persist the WebAuthn login challenge. This allows an attacker who captures a valid WebAuthn assertion to replay it indefinitely and authenticate as the user without interaction or hardware key.

References

Community reviews

Loading reviews…