Security readout for executives and security teams
Plain-English summary
phpMyFAQ’s WebAuthn login protection can fail to prevent reuse of a previously successful login response. An attacker who captures a valid assertion could repeatedly authenticate as that user without the hardware key or further user interaction, potentially gaining access to sensitive FAQ administration or content.
Executive priority
Urgent remediation is warranted for exposed deployments using WebAuthn because successful exploitation can bypass possession-based authentication and compromise confidentiality and integrity. Prioritize upgrading to 4.1.7 or later, while recognizing that the supplied evidence does not show exploitation in the wild.
Technical view
The login challenge created by prepareForLogin is not persisted because mutated WebAuthn key objects are not saved to the database. During authentication, a null guard then skips the anti-replay comparison. This permits indefinite replay of a captured successful assertion. The supplied version data is inconsistent, but the advisory title identifies versions before 4.1.7.
Likely exposure
Internet-accessible phpMyFAQ deployments using WebAuthn are the primary concern. The description identifies versions through 4.1.5 as affected, while the title says before 4.1.7. Confirm any ambiguity, including 4.1.6, against the vendor advisory.
Exploitation context
Exploitation requires obtaining a previously successful WebAuthn assertion, reflected by high attack complexity and a prerequisite condition in CVSS 4.0. Once captured, replay reportedly needs no privileges, user interaction, or hardware key. The supplied sources do not establish active exploitation, and this CVE is not listed as KEV.
Researcher notes
The failure spans challenge persistence and validation: both WebAuthn controllers reportedly omit saving mutated key objects, leaving the stored challenge null, while validation skips comparison under a null guard. CWE-294 and CVSS 4.0 score 9.1 are supplied. Version boundaries should be verified because the bundle separately states through 4.1.5 and before 4.1.7.
Mitigation direction
- Upgrade phpMyFAQ to version 4.1.7 or later, following the vendor advisory.
- Prioritize externally reachable deployments where WebAuthn login is enabled.
- Check vendor guidance for any additional containment or credential-response recommendations.
- Restrict unnecessary administrative exposure until affected systems are upgraded.
Validation and detection
- Inventory phpMyFAQ deployments and record their exact installed versions.
- Determine whether WebAuthn authentication is enabled or used on each deployment.
- Treat version 4.1.6 cautiously until the vendor advisory resolves the supplied version discrepancy.
- Confirm upgraded systems report phpMyFAQ 4.1.7 or later.
- Review authentication records for unusual repeated access involving WebAuthn-enabled accounts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-294: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-76214 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——VulnCheckCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.1CriticalVector: 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
Base CVSS 3.1 score
7.4HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-f534-wv9g-wx2w)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: phpMyFAQ before 4.1.7 WebAuthn Replay Attack via ChallengeCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authentication Bypass by Capture-replay
Authentication Bypass by Capture-replay represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.