CVE
thorsten/phpmyfaq authentication bypass in web installer
Affects phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2, specifically sites partway through the 3.1.x/3.2.x to 4.x upgrade. Fixed in 4.1.12 and 4.2.0-RC.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
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
- No known exploitation
- Fix
- Fixed in 4.1.12, 4.2.0-RC.2
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 41/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authentication bypass vulnerability because the web installer ignores the legacy config/database.php during 3.x upgrades. Unauthenticated attackers can reinstall the site against an attacker-controlled database and create their own administrator account to take over the application.
Who should check
Teams running phpMyFAQ 4.1.11 or earlier, or a 4.2.0 pre-release, including sites mid-upgrade from 3.1.x/3.2.x to 4.x with config/database.php kept.
“phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach10/20Affects Packagist packages
- Severity9.2/10CVSS 9.2
- No patch0/5No signal
What would change the score
- Would score about 81 if added to CISA KEV
- Would score about 76 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade 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-130371 (phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 Unauthenticated Reinstall via Web Installer), 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-130371 (entry last updated 2026-11-17):
Affected:
- Packagist package thorsten/phpmyfaq: 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):
- Site is mid-upgrade from 3.1.x/3.2.x to 4.x: legacy config/database.php kept, new package copied in, and /update not yet completed. (source: https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-jhf3-22r2-88hm)
- The web installer's already-installed check only looks at content/core/config/database.php, not the legacy 3.x config directory. (source: https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-jhf3-22r2-88hm)
- Affects phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2. (source: https://www.vulncheck.com/advisories/phpmyfaq-before-4.1.12-and-4.2.0-alpha-before-4.2.0-rc.2-unauthenticated-reinstall-via-web-installer)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130371 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130371 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-jhf3-22r2-88hm
- https://github.com/thorsten/phpMyFAQ/commit/eae6674d64bb6f53caf703d3f38b657f0c16a13c
- 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-before-4.1.12-and-4.2.0-alpha-before-4.2.0-rc.2-unauthenticated-reinstall-via-web-installer
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-130371
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-130371"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- thorsten/phpmyfaqPackagist
fixed in 4.1.12; From 4.2.0-alpha · fixed in 4.2.0-RC.2
Evidence 7
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- Patch
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130371
Is CVE-2026-130371 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. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The web installer can be run again without logging in, even on a live site. An attacker can point it at their own database and create a super-admin account on the victim's site. On the SQLite variant, this can also lead to code execution.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-130371?
thorsten/phpmyfaq (Packagist): 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 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 are affected. The setup at risk is a site mid-upgrade from 3.1.x/3.2.x to 4.x, where the new files are deployed, the legacy config/database.php is kept, and the /update step has not been completed. Check the installed version and whether /update has been run to see which case applies.Source: github.com, vulncheck.com
How do I fix CVE-2026-130371?
Upgrade to 4.1.12 or 4.2.0-RC.2. If you are in the middle of the 3.x to 4.x upgrade, complete the /update step.Source: github.com, vulncheck.com