CVE-2026-130371
Deferred Deferred - Pending Action

Authentication Bypass in phpMyFAQ via Web Installer

Vulnerability report for CVE-2026-130371, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-17

Last updated on: 2026-11-17

Assigner: VulnCheck

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-17
Last Modified
2026-11-17
Generated
2026-11-17
AI Q&A
2026-11-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
phpmyfaq phpmyfaq to 4.1.12 (exc)
phpmyfaq phpmyfaq to 4.2.0-alpha (exc)
phpmyfaq phpmyfaq to 4.2.0-RC.2 (exc)
phpmyfaq phpmyfaq to 4.2.0-rc.2 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is an authentication bypass vulnerability in phpMyFAQ versions before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2. During upgrades from version 3.x to 4.x, the web installer ignores the legacy config/database.php file. Unauthenticated attackers can exploit this to reinstall the application using an attacker-controlled database, create an admin account, and fully compromise the system.

Detection Guidance

Check if your phpMyFAQ instance is in the middle of an upgrade from version 3.x to 4.x by verifying if the web installer is still accessible without authentication. Look for the presence of legacy config/database.php alongside the new content/core/config/database.php file. If the installer at /setup/index.php is still active, it may indicate exposure.

Impact Analysis

An attacker could gain full control of your phpMyFAQ site, including database access and super-admin privileges. If SQLite is used and stored in a web-accessible directory, remote code execution may also be possible. The attack requires the site to be in the middle of a 3.1/3.2 to 4.x upgrade with new files deployed but the /update process not yet completed.

Compliance Impact

This vulnerability allows unauthenticated attackers to gain full administrative control over the phpMyFAQ application by reinstalling it with an attacker-controlled database. This could lead to unauthorized access to sensitive data, including personal or health information, which would violate GDPR and HIPAA compliance requirements for data protection and access controls.

Mitigation Strategies

Immediately upgrade phpMyFAQ to version 4.1.12 or 4.2.0-RC.2 or later. Ensure the web installer is no longer accessible and remove any legacy config/database.php files if they are not needed. Verify that the installer's checkInstallation() function now properly detects all database configurations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130371. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...