CVE-2026-47132
Deferred Deferred - Pending Action

Authenticated SQL LIKE Wildcard Injection in phpMyFAQ

Publication date: 2026-09-24

Last updated on: 2026-09-24

Assigner: GitHub, Inc.

Description
phpMyFAQ is an open source FAQ web application. Prior to version 4.2.0-alpha, an authenticated SQL LIKE wildcard injection vulnerability in phpMyFAQ’s chat user search allows any logged-in user to bypass the intended display-name search filter and enumerate active users. The endpoint escapes SQL string syntax but does not escape `%` and `_`, which remain active `LIKE` wildcards. Version 4.2.0-alpha patches the issue.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-24
Last Modified
2026-09-24
Generated
2026-10-15
AI Q&A
2026-09-24
EPSS Evaluated
2026-10-13
NVD
CVE-2026-47132
EUVD
EUVD-2026-86290

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
phpmyfaq phpmyfaq to 4.2.0-alpha (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-20 The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is an authenticated SQL LIKE wildcard injection vulnerability in phpMyFAQ's chat user search feature. It allows logged-in users to bypass display-name search filters and enumerate active users by exploiting unescaped wildcard characters (% and _) in SQL LIKE queries.

Detection Guidance

To detect this vulnerability, check phpMyFAQ logs for unusual chat search queries containing wildcards like '%%' or '__'. Monitor database queries for LIKE clauses with unescaped wildcards. Test by logging in and searching for users with queries like q=%% or q=__ to see if all user IDs and display names are returned.

Impact Analysis

An attacker could retrieve all active user IDs and display names, potentially exposing sensitive account information like internal user identities, staff names, or department details. This requires only low attack complexity and basic user privileges.

Compliance Impact

This vulnerability could lead to unauthorized exposure of personal or sensitive user data, which may violate GDPR's data protection requirements or HIPAA's privacy rules regarding protected health information.

Mitigation Strategies

Upgrade phpMyFAQ to version 4.2.0-alpha or later to patch the SQL LIKE wildcard injection flaw. If immediate upgrade is not possible, restrict access to the chat search endpoint or disable the feature until patched. Review database permissions to limit exposure of sensitive user information.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-47132. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart