# CVE-2026-76207: phpMyFAQ before 4.1.7 2FA Bypass via Remember-Me Cookie

> Attackers with valid credentials can bypass two-factor authentication by replaying remember-me cookies issued before verification, gaining unauthorized access.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-hvj7-4fmg-53cr, GHSA-jvxm-3fc5-8pjr

## What is CVE-2026-76207?

CVE-2026-76207 is a high-severity authentication bypass vulnerability in Phpmyfaq Phpmyfaq, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

phpMyFAQ before 4.1.7 contains a two-factor authentication bypass vulnerability where remember-me tokens are issued before 2FA verification completes. Attackers with valid credentials can obtain a remember-me cookie, skip the 2FA challenge, and replay the cookie to gain full authenticated access without second-factor verification.

Weakness: CWE-304 (Missing Critical Step in Authentication)

## Which versions are affected by CVE-2026-76207?

It affects 1 product.


Products: Phpmyfaq Phpmyfaq.

## How do I fix CVE-2026-76207?

No fix has been published for CVE-2026-76207 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-76207 being exploited?

There is no known exploitation of CVE-2026-76207 in the wild and no public exploit code.

## Other vulnerabilities in Phpmyfaq Phpmyfaq

- [CVE-2023-0310](https://insights.sbomify.com/CVE-2023-0310/): Cross-site Scripting (XSS) - Stored in thorsten/phpmyfaq (critical 9.8)
- [CVE-2022-4407](https://insights.sbomify.com/CVE-2022-4407/): Cross-site Scripting (XSS) - Reflected in thorsten/phpmyfaq (critical 9.8)
- [CVE-2017-11187](https://insights.sbomify.com/CVE-2017-11187/): Security feature bypass in n/a (critical 9.8)
- [CVE-2026-76213](https://insights.sbomify.com/CVE-2026-76213/): phpMyFAQ before 4.1.7 2FA Brute-Force via Session-Scoped Throttle (critical 9.1)
- [CVE-2026-76214](https://insights.sbomify.com/CVE-2026-76214/): phpMyFAQ before 4.1.7 WebAuthn Replay Attack via Challenge (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76207 and fix it if it is affected.

What it is: CVE-2026-76207 is a high-severity authentication bypass vulnerability in Phpmyfaq Phpmyfaq, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76207 in the wild and no public exploit code.

Affected product: Phpmyfaq Phpmyfaq. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-76207/ (Markdown: https://insights.sbomify.com/CVE-2026-76207/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76207
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76207
- OSV: https://osv.dev/vulnerability/CVE-2026-76207

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-76207/
Summaries are generated and may contain mistakes; the official description above is the record.