phpMyFAQ: SQL LIKE Wildcard Injection in Chat User Search Allows Authenticated User Enumeration (CVE-2026-47132)
phpMyFAQ version 4.2.0-alpha contains an authenticated SQL LIKE wildcard injection vulnerability in its chat user search API. This flaw allows any logged-in user to inject SQL LIKE wildcards (%) and (_) into search queries, bypassing intended display-name filtering and enabling enumeration of active user IDs and display names. The vulnerability is due to improper escaping of SQL LIKE metacharacters. A patch is available to address this issue. The vulnerability has a medium severity with a CVSS score of 5.4.
AI Analysis
Technical Summary
An authenticated SQL LIKE wildcard injection vulnerability exists in phpMyFAQ version 4.2.0-alpha's chat user search API. The input escaping mechanism fails to neutralize SQL LIKE metacharacters (%) and (_), allowing logged-in users to manipulate search queries to enumerate active user IDs and display names. This leads to potential disclosure of sensitive internal user information. The vulnerability is confirmed by proof of concept queries that return all active users when wildcards are injected. A patch is available to fix this issue.
Potential Impact
An authenticated user can bypass intended display-name filtering in the chat user search API by injecting SQL LIKE wildcards, enabling enumeration of active user IDs and display names. This can lead to disclosure of sensitive internal user information. The vulnerability does not affect availability and requires authentication, with a medium severity impact (CVSS 5.4).
Mitigation Recommendations
A patch is available for this vulnerability. Users should apply the official fix provided by the vendor to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
phpMyFAQ: SQL LIKE Wildcard Injection in Chat User Search Allows Authenticated User Enumeration (CVE-2026-47132)
Description
phpMyFAQ version 4.2.0-alpha contains an authenticated SQL LIKE wildcard injection vulnerability in its chat user search API. This flaw allows any logged-in user to inject SQL LIKE wildcards (%) and (_) into search queries, bypassing intended display-name filtering and enabling enumeration of active user IDs and display names. The vulnerability is due to improper escaping of SQL LIKE metacharacters. A patch is available to address this issue. The vulnerability has a medium severity with a CVSS score of 5.4.
CVSS v3.1
Score 5.4medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
An authenticated SQL LIKE wildcard injection vulnerability exists in phpMyFAQ version 4.2.0-alpha's chat user search API. The input escaping mechanism fails to neutralize SQL LIKE metacharacters (%) and (_), allowing logged-in users to manipulate search queries to enumerate active user IDs and display names. This leads to potential disclosure of sensitive internal user information. The vulnerability is confirmed by proof of concept queries that return all active users when wildcards are injected. A patch is available to fix this issue.
Potential Impact
An authenticated user can bypass intended display-name filtering in the chat user search API by injecting SQL LIKE wildcards, enabling enumeration of active user IDs and display names. This can lead to disclosure of sensitive internal user information. The vulnerability does not affect availability and requires authentication, with a medium severity impact (CVSS 5.4).
Mitigation Recommendations
A patch is available for this vulnerability. Users should apply the official fix provided by the vendor to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6pvm-2vjj-rx4w
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-47132"]
- Ecosystems
- ["Packagist"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a7c9b2cbf8831d539cdb5f6
Added to database: 08/12/2026, 16:11:24 UTC
Last enriched: 09/25/2026, 01:57:17 UTC
Last updated: 09/28/2026, 01:57:51 UTC
Views: 34
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.