Skip to main content
Vulnerability Database/CVE-2026-111887

CVE-2026-111887: phpMyFAQ Account Enumeration Vulnerability

CVE-2026-111887 is an account enumeration flaw in phpMyFAQ that lets attackers identify registered users through distinct HTTP responses. This post covers technical details, affected versions, impact, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-111887 Overview

CVE-2026-111887 is an account enumeration vulnerability in phpMyFAQ, an open source frequently asked questions (FAQ) application. The flaw affects phpMyFAQ versions before 4.1.9 and 4.2.0-alpha through versions before 4.2.0-beta. Unauthenticated attackers can confirm whether a given display name and email combination corresponds to a registered user by observing a distinct HTTP 409 response from the guest comment creation endpoint. The weakness is classified under CWE-204: Observable Response Discrepancy.

Critical Impact

Attackers can link user display names to email addresses at scale, enabling targeted phishing campaigns and credential-stuffing preparation against phpMyFAQ user bases.

Affected Products

  • phpMyFAQ versions prior to 4.1.9
  • phpMyFAQ 4.2.0-alpha through versions prior to 4.2.0-beta
  • Deployments exposing the guest comment creation endpoint to unauthenticated users

Discovery Timeline

  • 2026-10-17 - CVE-2026-111887 published to the National Vulnerability Database (NVD)
  • 2026-10-18 - Last updated in NVD database

Technical Details for CVE-2026-111887

Vulnerability Analysis

The vulnerability resides in the phpMyFAQ comment creation endpoint used to submit guest comments on FAQ entries. The endpoint accepts candidate user (display name) and mail (email) values alongside comment content. When an attacker submits a pair that matches an existing registered account, the server returns an HTTP 409 Conflict response. Non-matching pairs produce a different response code. This response discrepancy acts as a confirmation oracle for account existence.

Attackers do not need authentication, special privileges, or user interaction to probe the endpoint. The flaw does not permit code execution, data modification, or service disruption, but it does leak identity-linking information that supports follow-on social engineering attacks.

Root Cause

The root cause is an observable response discrepancy. The comment handler validates submitted identity values against the user database and returns distinguishable HTTP status codes based on whether the display name and email correspond to a registered account. The endpoint should return a uniform response regardless of account existence to avoid leaking enumeration data.

Attack Vector

An attacker iterates candidate user and mail pairs against the guest comment create endpoint using automated HTTP requests. A returned HTTP 409 confirms a registered account match. Harvested display name and email tuples enable targeted phishing, password spraying against the phpMyFAQ login or related services, and reconnaissance for business email compromise. See the GitHub Security Advisory GHSA-pgxw-7c68-83w7 and the VulnCheck advisory for phpMyFAQ for additional technical context.

Detection Methods for CVE-2026-111887

Indicators of Compromise

  • High volumes of POST requests to the phpMyFAQ comment create endpoint from a single source IP or a small cluster of IPs
  • Repeated requests cycling through many distinct user and mail parameter values
  • Elevated rates of HTTP 409 responses from the comment endpoint within a short time window
  • Requests originating from datacenter IP ranges, anonymizing proxies, or known scanning infrastructure

Detection Strategies

  • Baseline normal comment submission volume per source IP and alert on statistical outliers
  • Correlate 409 response patterns against unique user and mail parameter combinations to identify enumeration attempts
  • Deploy web application firewall (WAF) rules that rate-limit requests to the comment endpoint and flag enumeration signatures

Monitoring Recommendations

  • Enable detailed access logging on the phpMyFAQ web server with request bodies or parameter capture where privacy policy permits
  • Forward web and application logs to a centralized analytics platform for correlation across sources
  • Monitor for spikes in phishing reports from users whose emails are stored in the phpMyFAQ instance following suspected enumeration

How to Mitigate CVE-2026-111887

Immediate Actions Required

  • Upgrade phpMyFAQ to version 4.1.9 or later on the 4.1.x branch
  • Upgrade phpMyFAQ 4.2.0-alpha installations to 4.2.0-beta or later
  • Restrict access to the comment create endpoint using IP allowlists or authentication where feasible until patched
  • Review web server logs for prior enumeration activity and notify affected users of elevated phishing risk

Patch Information

The phpMyFAQ maintainers addressed the issue in versions 4.1.9 and 4.2.0-beta. The fix ensures the comment create endpoint returns uniform responses that do not disclose whether a given display name and email pair matches a registered account. Patch details are published in the GitHub Security Advisory GHSA-pgxw-7c68-83w7.

Workarounds

  • Place the phpMyFAQ instance behind a WAF with rate limiting on the comment endpoint to slow enumeration
  • Require CAPTCHA or proof-of-work challenges before accepting guest comment submissions
  • Temporarily disable guest commenting and require authenticated submissions until the patch is applied
bash
# Example nginx rate limit for the phpMyFAQ comment endpoint
limit_req_zone $binary_remote_addr zone=phpmyfaq_comment:10m rate=5r/m;

location ~ ^/api/v[0-9]+/comment {
    limit_req zone=phpmyfaq_comment burst=3 nodelay;
    limit_req_status 429;
    proxy_pass http://phpmyfaq_backend;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.