CVE-2026-108851 Details
Description
phpMyFAQ through 4.1.10 contains a missing authorization vulnerability in the MCP server faq_search tool that allows MCP clients to read restricted FAQs because Search::searchDatabase() never applies user or group permission checks. Attackers connected to the phpmyfaq:mcp:server can issue search queries to retrieve the full question and answer text of active FAQs restricted to specific users or groups.
A missing authorization vulnerability has been identified in phpMyFAQ versions through 4.1.10, specifically within the MCP server's FAQ search tool. This vulnerability allows MCP clients to access restricted FAQs because the search function does not apply necessary user or group permission checks. Attackers connected to the phpMyFAQ MCP server can send search queries that retrieve the full text of questions and answers from active FAQs, even those limited to specific users or groups.
The vulnerability can be addressed by applying the same user and group permission checks to the MCP FAQ search tool that are used in regular FAQ retrieval. This involves modifying the database search function to include the necessary permission predicates, ensuring that restricted content is not returned to unauthorized users.
Metrics
CVSS 4.0 Severity and Vector Strings:
VolerionCVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Oct 11, 2026CISA-ADP
Assessed Oct 13, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-862 | Missing Authorization | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| phpMyFAQ | >= 4.1.0, <= 4.1.10 (semver) |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 13, 2026 | CVE Modified | CISA-ADP |
| Oct 11, 2026 | New CVE Received | [email protected] |