# CVE-2026-111886: phpMyFAQ 4.2.0-alpha.2 before 4.2.0-beta 2FA Brute-Force via remove-twofactor Endpoint

> Authenticated attackers can brute-force TOTP codes via the remove-twofactor endpoint to disable 2FA and take over accounts.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/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-7pjw-6v4g-f837, GHSA-9p2j-4h8p-3832

## What is CVE-2026-111886?

CVE-2026-111886 is a high-severity 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 from 4.2.0-alpha.2 before 4.2.0-beta lacks brute-force lockout in the removeTwofactorConfig() 2FA removal endpoint, allowing authenticated attackers to guess TOTP codes without limit. Attackers holding a hijacked session and CSRF token can repeatedly POST guesses to /api/user/remove-twofactor to permanently disable the victim's 2FA.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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


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

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

## Is CVE-2026-111886 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111886 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111886 is a high-severity 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111886 exists.

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

## Sources

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

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