Information Exposure Affecting thorsten/phpmyfaq package, versions <4.1.9>=4.2.0-alpha, <4.2.0-beta
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-PHP-THORSTENPHPMYFAQ-21717201
- published26 Oct 2026
- disclosed17 Oct 2026
- creditzx
Introduced: 17 Oct 2026
NewCVE-2026-111887 (opens in a new tab)How to fix?
Upgrade thorsten/phpmyfaq to version 4.1.9, 4.2.0-beta or higher.
Overview
thorsten/phpmyfaq is a FAQ system for PHP and MySQL, PostgreSQL and other databases
Affected versions of this package are vulnerable to Information Exposure via the guest comment create endpoint (CommentController.php), where the not-logged-in branch performs two independent exact-match existence lookups (User::checkDisplayName and User::checkMailAddress) and returns a uniquely distinguishable HTTP 409 Conflict response when both the submitted display name and email address match a registered account. Every other outcome returns HTTP 200, 400, 403, or 404, making the 409 a clean binary oracle for account existence and name-to-email linkage. An unauthenticated attacker can submit guest comments with candidate user and mail values to confirm whether an arbitrary display name and email correspond to a registered account, enabling targeted phishing, credential-stuffing target selection, and deanonymization of pseudonymous users.