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.
Published: 2026-09-24
Score: 5.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Authenticated User Enumeration
Action: Apply Patch
AI Analysis

Impact

The phpMyFAQ web application is vulnerable to an SQL LIKE wildcard injection in its chat user search endpoint. Because the application escapes the usual SQL string delimiters but fails to sanitize the '%' and '_' characters, an authenticated user can craft a search term that expands into a pattern matched by all database records. This allows the user to enumerate the usernames or display names of all active users. The flaw does not provide direct data leakage beyond identifiers nor does it enable code execution, but it exposes a modest amount of user information that could be useful for follow‑on attacks.

Affected Systems

All installations of the open source phpMyFAQ application distributed by the vendor thorsten, specifically any version earlier than 4.2.0‑alpha that includes the chat user search feature. The vulnerability affects all environments that deploy this code and allow users to log in and access the chat search interface.

Risk and Exploitability

The vulnerability carries a CVSS base score of 5.4, indicating a moderate impact. There is no EPSS value available, and the flaw is not included in CISA’s KEV catalog. Because the privilege requirement is authenticated, the attack vector is internal or privileged user. The impact is limited to enumeration of active users; no disclosure of more sensitive data or remote code execution is possible. Exploitation requires a logged‑in user with access to the chat search, which is typically a regular user or administrator and therefore does not increase the risk profile significantly beyond the moderate score.

Generated by OpenCVE AI on September 25, 2026 at 06:25 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade phpMyFAQ to version 4.2.0‑alpha or later, the release that removes the injection vulnerability.
  • If an update is not currently feasible, immediately disable the chat user search endpoint or restrict its use to a trusted administrator group until a patched version is deployed.
  • Review all search functionalities within phpMyFAQ and ensure that wildcard characters are properly escaped or quoted to prevent repeat occurrences of similar injection flaws.

Generated by OpenCVE AI on September 25, 2026 at 06:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-6pvm-2vjj-rx4w phpMyFAQ: SQL LIKE Wildcard Injection in Chat User Search Allows Authenticated User Enumeration
History

Thu, 24 Sep 2026 19:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 24 Sep 2026 19:15:00 +0000

Type Values Removed Values Added
First Time appeared Thorsten
Thorsten phpmyfaq
Vendors & Products Thorsten
Thorsten phpmyfaq

Thu, 24 Sep 2026 17:00:00 +0000

Type Values Removed Values Added
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.
Title phpMyFAQ: SQL LIKE Wildcard Injection in Chat User Search Allows Authenticated User Enumeration
Weaknesses CWE-20
CWE-200
CWE-89
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}


Subscriptions

Thorsten Phpmyfaq
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-24T17:06:31.893Z

Reserved: 2026-05-18T19:50:18.695Z

Link: CVE-2026-47132

cve-icon Vulnrichment

Updated: 2026-09-24T17:06:14.650Z

cve-icon NVD

Status : Deferred

Published: 2026-09-24T17:17:04.723

Modified: 2026-09-24T18:17:13.453

Link: CVE-2026-47132

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-25T06:30:06Z

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')