thorsten/phpmyfaq cross-tenant account takeover in WebAuthn registration
Only affects phpMyFAQ multisite setups with WebAuthn enabled, where client instances and the master share one PHP session store. Fixed in 4.1.12 and 4.2.0-RC.2.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 4.1.12, 4.2.0-RC.2
- Who is exposed
- Specific setups only
Summary
Written by a model
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.
Who should check
Teams running phpMyFAQ 4.1.9 to before 4.1.12, or 4.2.0-alpha before 4.2.0-RC.2, in multisite deployments with WebAuthn passkeys enabled.
“contains an authorization bypass vulnerability in multisite deployments”
What to do
Check whether your setup matches what the bug needs.
Multisite deployment where client instances and the master share one PHP session store WebAuthn support enabled (security.enableWebAuthnSupport=true), which is off by default Open self-registration on a client tenant (the default), so the victim login does not exist thereUpgrade to a fixed version: 4.1.12, 4.2.0-RC.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by 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), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130369 (entry last updated 2026-11-18):
Affected:
- Packagist package thorsten/phpmyfaq: from 4.1.9, fixed in 4.1.12; from 4.2.0-alpha, fixed in 4.2.0-RC.2
Fixed versions: 4.1.12, 4.2.0-RC.2.
Conditions (all must be true for the bug to be hit):
- Multisite deployment where client instances and the master share one PHP session store (source: https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-j82j-jp9w-f75c)
- WebAuthn support enabled (security.enableWebAuthnSupport=true), which is off by default (source: https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-j82j-jp9w-f75c)
- Open self-registration on a client tenant (the default), so the victim login does not exist there (source: https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-j82j-jp9w-f75c)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130369 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130369 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-j82j-jp9w-f75c
- https://github.com/thorsten/phpMyFAQ/commit/8a7eeddddda7f11882d1e9944ab92473c6890b85
- https://github.com/thorsten/phpMyFAQ/releases/tag/4.1.12
- https://github.com/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2
- https://www.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-takeover
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130369
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130369"}.Affected versions
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach10/20Affects Packagist packages
- Severity10/10CVSS 9.2, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now1 day
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Public exploit activity
- EPSS: 0.45%
- Posted on X by cve.now Nov 17
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 7
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · thorsten/phpMyFAQ · Advisory GHSA-j82j-jp9w-f75c |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130369 |
| Record | NVD · CVE-2026-130369 |
| Other links 4 | |
| Patch | GitHub · thorsten/phpMyFAQ · Commit 8a7eeddd |
| Repository | GitHub · thorsten/phpMyFAQ · Release 4.1.12 |
| Repository | GitHub · thorsten/phpMyFAQ · Release 4.2.0-RC.2 |
| Link | 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-takeover |
Questions about CVE-2026-130369
Is CVE-2026-130369 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
An anonymous attacker can overwrite the passkeys of an account on another tenant or the master, then log in as that account, such as admin.
Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-130369?
thorsten/phpmyfaq (Packagist): from 4.1.9 before 4.1.12; from 4.2.0-alpha before 4.2.0-RC.2.
Source: cve.now feed data
Am I affected, and how do I check?
Versions from 4.1.9 before 4.1.12, and from 4.2.0-alpha before 4.2.0-RC.2. The setup must be a multisite deployment where client instances and the master share one PHP session store, WebAuthn must be enabled (security.enableWebAuthnSupport=true, off by default), and self-registration must be open on a client tenant (the default). Check the installed version and the security.enableWebAuthnSupport and security.enableRegistration settings.
Source: github.com, vulncheck.com
How do I fix CVE-2026-130369?
Upgrade to phpMyFAQ 4.1.12 on the 4.1 line, or to 4.2.0-RC.2 on the 4.2 line.
Source: github.com, vulncheck.com
Related
- CVE-2026-130351phpMyFAQ 4.2.0-alpha before 4.2.0-RC.2 Cross-Tenant Configuration Overwrite via Redis Store
- CVE-2026-130357phpMyFAQ 4.2.0-alpha.2 before 4.2.0-RC.2 Privilege Escalation via updateUserRights
- CVE-2026-130348phpMyFAQ 4.1.0 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 Category ACL Bypass
- CVE-2026-130352phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 Private Notes Disclosure via FAQ API
- CVE-2026-130353phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 FAQ API Email Disclosure
- CVE-2026-130354phpMyFAQ 4.1.0 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 Authentication Bypass via WebAuthn Prepare
No corrections so far. Something wrong on this page? Report an error.