Vulnerability in thorsten/phpmyfaq (CVE-2026-47132)
Summary
Vulnerability in thorsten/phpmyfaq (CVE-2026-47132). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/chat/users. Mitigation: upgrade to 4.2.0-alpha or later.
Original description
The description as published by the source.
Summary
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.
Details
The vulnerable endpoint is:
GET /api/chat/users?q=...
Source:
// phpmyfaq/src/phpMyFAQ/Controller/Frontend/Api/ChatController.php
$query = trim($request->query->get('q', ''));
if (mb_strlen($query) < 2) {
return $this->json([
'success' => true,
'users' => [],
], Response::HTTP_OK);
}
$chat = new Chat($this->configuration);
$users = $chat->searchUsers($query, $this->currentUser->getUserId());
Sink:
// phpmyfaq/src/phpMyFAQ/Chat.php
$escapedTerm = $this->configuration->getDb()->escape(mb_strtolower($searchTerm));
$query = sprintf(
"SELECT u.user_id, ud.display_name
FROM %sfaquser u
LEFT JOIN %sfaquserdata ud ON u.user_id = ud.user_id
WHERE u.user_id != %d
AND u.user_id > 0
AND LOWER(ud.display_name) LIKE '%%%s%%'
AND u.account_status = 'active'
LIMIT %d",
Database::getTablePrefix(),
Database::getTablePrefix(),
$excludeUserId,
$escapedTerm,
$limit,
);
escape() prevents SQL string breakout, but it does not escape SQL LIKE metacharacters. Therefore, attacker-contro…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47132 has been found in thorsten/phpmyfaq.
Attackers can target a specific entry point like GET /api/chat/users over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade thorsten/phpmyfaq to 4.2.0-alpha or later.
If unsure, ask your IT team or search "thorsten/phpmyfaq CVE-2026-47132" on the vendor's site.
CVE-2026-47132 (thorsten/phpmyfaq) — CWE-20 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/chat/users / LIKE
Patched: 4.2.0-alpha — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in thorsten/phpmyfaq. Attackers reach the vulnerable code path via GET /api/chat/users.
Check the vendor advisory for the affected versions of thorsten/phpmyfaq. Attack surface: GET /api/chat/users / LIKE.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 4.2.0-alpha.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/chat/users requests with malformed payloads or SQL meta-characters. Run grep -r 'thorsten/phpmyfaq' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'thorsten/phpmyfaq' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
thorsten/phpmyfaqを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/chat/users' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/chat/usersへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade thorsten/phpmyfaq to 4.2.0-alphaステージング環境で 4.2.0-alpha に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/chat/users on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov