# CVE-2026-111882: phpMyFAQ 3.2.0-alpha before 4.1.9 and 4.2.0-alpha before 4.2.0-beta TOTP 2FA Bypass via SSO Callbacks

> Attackers with valid IdP credentials can bypass TOTP 2FA via SSO callbacks to gain full authenticated access, including admin privileges.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** GHSA-74rq-7w8c-gr94

## What is CVE-2026-111882?

CVE-2026-111882 is a high-severity authentication bypass vulnerability in thorsten phpMyFAQ, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

phpMyFAQ 3.2.0-alpha before 4.1.9 and 4.2.0-alpha before 4.2.0-beta contains an authentication bypass vulnerability that allows IdP-authenticated users to skip TOTP two-factor authentication through the Keycloak and Entra ID SSO callbacks. Attackers holding a valid or phished IdP identity linked to a 2FA-enabled account can complete the OIDC flow and obtain a fully authenticated session, including administrator accounts.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-111882 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111882 is a high-severity authentication bypass vulnerability in thorsten phpMyFAQ, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-111882 in the wild and no public exploit code.

Affected product: thorsten 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-111882/ (Markdown: https://insights.sbomify.com/CVE-2026-111882/index.md)
```

## Sources

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

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