← Back
CVE-2026-49205
medium
CVSS 6.5
Vulnerability in thorsten/phpmyfaq (CVE-2026-49205)
Summary
vulnerability in thorsten/phpmyfaq (CVE-2026-49205). Confidential information can be exposed externally. Exploitable via `POST /api/v4.0/category`. Mitigation: upgrade to `4.1.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-49205** has been found in thorsten/phpmyfaq.
Attackers can target a specific entry point like `POST /api/v4.0/category` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade thorsten/phpmyfaq to **4.1.4** or later.
If unsure, ask your IT team or search "thorsten/phpmyfaq CVE-2026-49205" on the vendor's site.
CVE-2026-49205 (thorsten/phpmyfaq) — CWE-862 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v4.0/category / POST /api/v4.0/faq / PUT /api/v4.0/faq / POST /api/v4.0/question
Patched: `4.1.4` — 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.
❓ What is the problem
**A vulnerability** (CWE-862) exists in thorsten/phpmyfaq. Attackers reach the vulnerable code path via `POST /api/v4.0/category` without authentication.
📍 Affected scope
thorsten/phpmyfaq — . Attack surface: POST /api/v4.0/category / POST /api/v4.0/faq / PUT /api/v4.0/faq / POST /api/v4.0/question.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **4.1.4**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `POST /api/v4.0/category` 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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /api/v4.0/category' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /api/v4.0/category` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade thorsten/phpmyfaq to 4.1.4ステージング環境で 4.1.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /api/v4.0/category on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
thorsten/phpmyfaq
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.4"}]}]
composer
phpmyfaq/phpmyfaq
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.4"}]}]