Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessConnect to phpmyfaq:mcp:server as MCP client
-
ExploitIssue faq_search query via MCP tool
-
ExecutionSearch::searchDatabase() skips permission checks
-
ImpactReceive restricted FAQ question/answer text
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the optional phpMyFAQ MCP server feature is enabled and that the attacker can connect to phpmyfaq:mcp:server as an MCP client with at least low-privilege access (CVSS PR:L) - it is not a remote-unauthenticated flaw. The affected feature is specifically the faq_search tool, whose executor calls Search::searchDatabase() without applying the per-user/per-group permission checks that normally restrict FAQ visibility. Exploitation is limited to confidentiality (reading question/answer text of active, access-restricted FAQs); there is no write, modification, or availability impact. Key limiting factors: the MCP server must be deployed and reachable (non-default for many installs), the attacker needs an authenticated/privileged MCP connection, the attack vector is local rather than network-facing, and only FAQs that are active and restricted are exposed. |
| Impact | This is a genuine but modest-priority issue, not a high-urgency flaw. The input CVSS 4.0 base score is 4.8 (Medium) with vector AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N - a local attack vector, low complexity, but requiring low-level privileges (PR:L) and yielding only limited confidentiality impact (VC:L) with no integrity or availability impact. In plain terms, an actor who already holds some authenticated access to the MCP server can read restricted FAQ content they should not see; they cannot modify data or crash the service. There is NO EPSS score in the provided data and NO CISA KEV listing, so there is no quantitative exploitation-probability signal and no evidence of active exploitation. No SSVC decision record was supplied either. No explicit POC flag was provided, though VulnCheck and a hackmd write-up document the mechanism (Search::searchDatabase() omitting user/group permission checks). The signals are internally consistent - a low-privilege, local, confidentiality-only authorization gap - so there is no contradiction to flag, but defenders should note the key missing signals (EPSS and KEV absent) mean real-world exploitation likelihood is unquantified and should be treated as low absent further intelligence. |
| Exploit ScenarioDerived | An actor with low-privilege access to a phpMyFAQ instance that has the MCP server enabled connects as an MCP client to phpmyfaq:mcp:server and invokes the faq_search tool. Because Search::searchDatabase() never applies user or group permission filters, the search returns the full question and answer text of FAQs that were restricted to specific users or groups, disclosing information the actor was not authorized to read. No public exploit identified at time of analysis, though the vulnerable code paths are documented in the references. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 11, 2026
Missing authorization in the phpMyFAQ MCP server's faq_search tool allows an authenticated MCP client to read the full question-and-answer text of active FAQs that are restricted to specific users or groups, because the underlying Search::searchDatabase() routine never applies the per-user or per-group permission checks that normally govern FAQ visibility. The flaw affects phpMyFAQ through 4.1.10 and is limited to confidentiality: exploitation requires that the optional MCP server feature is deployed and reachable and that the attacker can connect to phpmyfaq:mcp:server with at least low-privilege access (CVSS PR:L, local attack vector), so this is a modest-priority issue rather than a high-urgency flaw. No public exploit identified at time of analysis and no vendor-released patch identified at time of analysis; the issue is tracked under CWE-862 (Missing Authorization).
RemediationAI
No vendor-released patch identified at time of analysis, so remediation must be compensating: the most direct control is to disable or uninstall the optional MCP server feature on phpMyFAQ hosts that do not require it, which eliminates the exposure entirely at the cost of losing MCP-based integrations; if MCP must remain, restrict reachability of the phpmyfaq:mcp:server endpoint to a trusted local host or an allow-listed management network segment (for example via reverse-proxy or firewall rules) and require strong, uniquely issued MCP client credentials, accepting that this only raises the bar for an attacker who already holds low-privilege access rather than fixing the missing check. Where the affected tool cannot be disabled or segmented, reduce blast radius by deactivating or re-classifying the FAQs whose question and answer text must stay user- or group-restricted, and monitor MCP query logs for broad or enumeration-style faq_search calls that would indicate abuse. Until an upstream fix is published, watch https://github.com/thorsten/phpMyFAQ and the VulnCheck advisory at https://www.vulncheck.com/advisories/phpmyfaq-through-4.1.10-missing-authorization-via-mcp-server-faq-search-tool for a patched release, and re-apply the authorization predicates used elsewhere in the application to Search::searchDatabase() if maintaining a local code fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
phpMyFAQ is a PHP-based FAQ/knowledge-base application from vendor Thorsten (CPE cpe:2.3:a:thorsten:phpmyfaq, wildcard version covering all releases through 4.1.10). Recent 4.x releases ship an optional MCP (Model Context Protocol) server component that exposes tools such as faq_search to MCP clients; the tool's executor, FaqSearchToolExecutor (phpmyfaq/src/phpMyFAQ/Service/McpServer/FaqSearchToolExecutor.php, lines 56-102), delegates to Search::searchDatabase() (phpmyfaq/src/phpMyFAQ/Search.php, lines 137-194). That search routine builds and executes FAQ queries without injecting the user- or group-based visibility predicates that the normal web-facing search path uses, so every active FAQ row is returned regardless of its configured user/group restrictions. The root cause is CWE-862 Missing Authorization: an authorization decision that exists elsewhere in the application is simply absent from this code path, leaving the permission model enforced only at the presentation/controller layer rather than in the data-access layer. Impact is confined to information disclosure (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N; vendor-published CVSS 4.0 base score 4.8) since the tool only performs read queries.
Know when Phpmyfaq gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Requires an authenticated low-privilege MCP connection (PR:L) over a local MCP channel (AV:L), low complexity, and leaks only restricted FAQ text (C:L) with no integrity or availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Duplicate-email registration handling in phpMyFAQ 4.0.7 through 4.0.13 (and 4.0-nightly-2025-10-03 and earlier) lets una
Insufficient Session Expiration in GitHub repository thorsten/phpmyfaq prior to 3.2.2. Rated critical severity (CVSS 9.8
Authentication Bypass by Capture-replay in GitHub repository thorsten/phpmyfaq prior to 3.1.12. Rated critical severity
Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.12. Rated critical severity (CVSS 9.8), t
Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.8. Rated critical severity (CVSS 9.8), th
Unauthenticated SQL injection in phpMyFAQ before 4.1.2 allows remote attackers to extract credentials, admin tokens, and
In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.ratings.php. Rated high severity (CVS
In phpMyFaq before 2.9.9, there is CSRF in admin/ajax.config.php. Rated high severity (CVSS 8.8), this vulnerability is
In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) for modifying a glossary. Rated high severity (CVSS
In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.main.php. Rated high severity (CVSS 8
phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. Rated high severi
phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. Rated high severi
EUVD-2026-97002
GHSA-52xr-g583-rx96
NVD
CVE.org
EPSS
Exploit-DB