# CVE-2026-130369: phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 Cross-Tenant WebAuthn Account Takeover


- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-29w5-2rqq-hh6x, GHSA-j82j-jp9w-f75c

## What is CVE-2026-130369?

CVE-2026-130369 is a critical vulnerability in thorsten phpMyFAQ, published on 17 Nov 2026. 

### Official description

phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authorization bypass vulnerability in multisite deployments that allows attackers to overwrite passkeys of accounts on other tenants via a shared PHP session store. Attackers can run WebAuthn prepare() for a login on one tenant, then replay the session against /api/webauthn/register on another tenant or the master to replace that user's passkeys and log in as admin.

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

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

2 open source packages ship an affected version, including thorsten/phpmyfaq.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `thorsten/phpmyfaq` | Packagist | `pkg:composer/thorsten/phpmyfaq` | From 4.1.9 | 4.1.12 |
| `thorsten/phpmyfaq` | Packagist | `pkg:composer/thorsten/phpmyfaq` | From 4.2.0-alpha | 4.2.0-RC.2 |

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

Upgrade thorsten/phpmyfaq to a fixed version for your release line: 4.1.12 or 4.2.0-RC.2.

## Is CVE-2026-130369 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130369 is a critical vulnerability in thorsten phpMyFAQ, published on 17 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130369 exists.

Affected packages and fixed versions:
- thorsten/phpmyfaq (Packagist): affected from 4.1.9; fixed in 4.1.12
- thorsten/phpmyfaq (Packagist): affected from 4.2.0-alpha; fixed in 4.2.0-RC.2

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

## Sources

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

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