CVE-2026-111887: phpMyFAQ account enumeration via guest comment endpoint

CVE-2026-111887 · Severity: medium · CVSS 5.3 · Published 2026-10-17

phpMyFAQ is a frequently-asked-questions management system used by organizations to publish help content. The vulnerability allows unauthenticated attackers to determine whether specific display names and email addresses correspond to registered user accounts by submitting guest comments and observing HTTP response codes. An attacker can use this to link names to emails for targeted phishing attacks or to identify which credentials are worth attempting in credential-stuffing campaigns.

Technologies: Thorsten phpMyFAQ. Vendors: Thorsten.

Quick answers

Is CVE-2026-111887 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-111887 being exploited in the wild.
How severe is CVE-2026-111887?
Medium severity, with a CVSS score of 5.3, published 17 October 2026.
Which products and versions are affected?
Thorsten phpMyFAQ 4.0.0 to 4.1.8; 4.2.0-alpha to 4.2.0-beta (prior to 4.2.0-beta).
Is there a fix for CVE-2026-111887?
Yes: fixed in phpMyFAQ 4.1.9, 4.2.0-beta. Until then: Disable guest commenting by setting records.allowCommentsForGuests to false, or enable CAPTCHA on all comment submissions to add friction to enumeration attacks. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-111887 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-111887?
Check whether you run Thorsten phpMyFAQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: phpMyFAQ 4.1.9, 4.2.0-beta

Disable guest commenting by setting records.allowCommentsForGuests to false, or enable CAPTCHA on all comment submissions to add friction to enumeration attacks.

Technical details

The guest comment creation endpoint returns a distinct HTTP 409 Conflict response if and only if both a supplied display name and email match registered account credentials, while all other outcomes return 200, 400, 403, or 404. This violates the project's own anti-enumeration principle enforced in registration and password-reset flows. An unauthenticated attacker can reach the public endpoint with guest commenting enabled by default, bypass the CSRF check by fetching the token from public FAQ pages, and exploit this binary oracle to enumerate accounts and establish name-to-email linkages.

Affected products

  • thorsten phpMyFAQ 4.0.0 to 4.1.8; 4.2.0-alpha to 4.2.0-beta (prior to 4.2.0-beta)

Timeline

  • 2026-10-03: disclosed
  • 2026-10-17: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.