# CVE-2026-111905: phpMyFAQ 3.2.0 before 4.1.9 and 4.2.0-alpha before 4.2.0-beta IDOR Leaks TOTP Secret via /admin/api/user/data

> Delegated administrators can read SuperAdmin TOTP secrets via IDOR, enabling two-factor authentication bypass and account takeover.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-44gp-7cgr-6p92, GHSA-hp8j-w94m-j5c7

## What is CVE-2026-111905?

CVE-2026-111905 is a high-severity missing authorization vulnerability in thorsten phpMyFAQ, published on 17 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

phpMyFAQ 3.2.0 before 4.1.9 and 4.2.0-alpha before 4.2.0-beta contains an insecure direct object reference vulnerability in GET /admin/api/user/data/{userId}, which returns any user's full faquserdata row, including the live TOTP secret, without a SuperAdmin or protected-target check. Delegated administrators with user-management rights can read a SuperAdmin's TOTP secret and generate valid codes to bypass two-factor authentication.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-111905 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111905 is a high-severity missing authorization vulnerability in thorsten phpMyFAQ, published on 17 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111905 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-111905/ (Markdown: https://insights.sbomify.com/CVE-2026-111905/index.md)
```

## Sources

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

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