← Back
CVE-2026-46364 critical CVSS 9.8

SQL Injection in thorsten/phpmyfaq (CVE-2026-46364)

Summary

SQL injection in thorsten/phpmyfaq (CVE-2026-46364). Successful exploitation can lead to full system takeover. Exploitable via `GET /api/captcha`. Mitigation: upgrade to `4.1.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-46364** has been found in thorsten/phpmyfaq. Attackers can target a specific entry point like `GET /api/captcha` over the network to misuse the product. Successful exploitation can lead to full system takeover. CVSS score: 9.8/10. What to do: upgrade thorsten/phpmyfaq to **4.1.2** or later. If unsure, ask your IT team or search "thorsten/phpmyfaq CVE-2026-46364" on the vendor's site.
CVE-2026-46364 (thorsten/phpmyfaq) — CWE-89 / CVSS v3 9.8 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: GET /api/captcha / `sprintf` / `b9f25109` / `BuiltinCaptcha` Patched: `4.1.2` — 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
**SQL injection** (CWE-89) exists in thorsten/phpmyfaq. Attackers reach the vulnerable code path via `GET /api/captcha` without authentication.
📍 Affected scope
thorsten/phpmyfaq — . Attack surface: GET /api/captcha / `sprintf` / `b9f25109` / `BuiltinCaptcha`.
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **4.1.2**.
🛡️ 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 `GET /api/captcha` 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

  1. 1
    Identify exposure identify
    grep -r 'thorsten/phpmyfaq' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `thorsten/phpmyfaq` を grep し、稼働しているサービス・バージョンを把握する。

  2. 3
    Hunt for indicators of compromise detect
    grep 'GET /api/captcha' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで `GET /api/captcha` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 6
    Apply patch patch
    Upgrade thorsten/phpmyfaq to 4.1.2

    ステージング環境で 4.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify
    Replay attack against GET /api/captcha on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

composer thorsten/phpmyfaq
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.2"}]}]
composer phpmyfaq/phpmyfaq
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.2"}]}]
Packagist thorsten/phpmyfaq
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.2"}]}]
Packagist phpmyfaq/phpmyfaq
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.2"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →