CVE-2026-130351
Deferred Deferred - Pending Action

Authorization Bypass in phpMyFAQ via Redis Configuration Store

Vulnerability report for CVE-2026-130351, 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 from 4.2.0-alpha before 4.2.0-RC.2 contains an authorization bypass vulnerability in the multisite Redis configuration store that is not tenant-scoped. As a result, tenant administrators can read and overwrite the master instance's effective configuration. Attackers can save configuration through /admin/api/configuration, optionally resetting storage.redisPrefix, to redirect master SMTP, set a known API token, or alter authentication settings.

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 1 associated CPE
Vendor Product Version / Range
phpmyfaq phpmyfaq From 4.2.0-alpha (inc) to 4.2.0-RC.2 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in phpMyFAQ versions 4.2.0-alpha through 4.2.0-RC.2 allows tenant administrators to read and overwrite the master instance's Redis-based configuration settings due to improper tenant scoping. The Redis configuration store uses non-tenant-scoped keys, enabling tenant admins to access and modify critical configurations like SMTP relay, API tokens, and authentication settings.

Detection Guidance

Check if Redis is used for multisite configuration in phpMyFAQ versions 4.2.0-alpha to 4.2.0-RC.2. Inspect Redis keys for non-tenant-scoped entries and verify if tenant admins can access or modify master instance configurations via /admin/api/configuration.

Impact Analysis

Attackers could exploit this to redirect SMTP traffic, capture password-reset emails, set known API tokens, enable open registration, or alter authentication settings. This could lead to unauthorized access, data breaches, or loss of control over the master instance.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection requirements and HIPAA's security rules. It may result in data breaches, unauthorized disclosure, or loss of control over authentication systems, leading to compliance failures.

Mitigation Strategies

Upgrade phpMyFAQ to version 4.2.0-RC.2 or later. Ensure Redis keys are tenant-scoped and restrict non-master instances from editing storage-related keys. Reset sensitive Redis configurations during tenant provisioning.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130351. 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...