CVE-2026-130369 json
phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 Cross-Tenant WebAuthn Account Takeover
published yesterday modified yesterday also EUVD-2026-126778 , GHSA-j82j-jp9w-f75c
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository thorsten/phpMyFAQ. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- thorsten phpMyFAQ 4.1.12, 4.2.0-RC.2
Is CVE-2026-130369 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-17).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- thorsten phpMyFAQ
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
github.com
/thorsten/phpMyFAQ/commit/8a7eeddddda7f11882d1e9944ab92473c6890b85
patch
-
github.com
/thorsten/phpMyFAQ/security/advisories/GHSA-j82j-jp9w-f75c
vendor-advisory, advisory
-
github.com
/thorsten/phpMyFAQ/releases/tag/4.1.12
release-notes
-
github.com
/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2
release-notes
-
vulncheck.com
/advisories/phpmyfaq-4.1.9-before-4.1.12-and-4.2.0-alpha-before-4.2.0-rc.2-cross-tenant-webauthn-account-takeo
third-party-advisory
Sources
- CVE List CVE-2026-130369
- NVD CVE-2026-130369
- Maintainer advisory GHSA-j82j-jp9w-f75c
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of thorsten/phpMyFAQ published their own advisory on GitHub. Reviewed sources take precedence over it.