← Back
CVE-2026-45010
critical
CVSS 9.1
Vulnerability in thorsten/phpmyfaq (CVE-2026-45010)
Summary
vulnerability in thorsten/phpmyfaq (CVE-2026-45010). Confidential information can be exposed externally. Exploitable via `POST /admin/check`. Mitigation: upgrade to `4.1.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45010** has been found in thorsten/phpmyfaq.
Attackers can target a specific entry point like `POST /admin/check` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.1/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-45010" on the vendor's site.
CVE-2026-45010 (thorsten/phpmyfaq) — CWE-307 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /admin/check / `AuthenticationController` / `SkipsAuthenticationCheck` / `token`
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
**A vulnerability** (CWE-307) exists in thorsten/phpmyfaq. Attackers reach the vulnerable code path via `POST /admin/check` without authentication.
📍 Affected scope
thorsten/phpmyfaq — . Attack surface: POST /admin/check / `AuthenticationController` / `SkipsAuthenticationCheck` / `token`.
🔥 Severity
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally
🔧 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 `POST /admin/check` 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 /admin/check' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /admin/check` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade thorsten/phpmyfaq to 4.1.2ステージング環境で 4.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /admin/check 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
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-45010
- package https://github.com/thorsten/phpMyFAQ
- web https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-9pq7-mfwh-xx2j
- web https://www.vulncheck.com/advisories/phpmyfaq-unauthenticated-two-factor-authentication-brute-force-via-admin-check-endpoint
- web https://github.com/advisories/GHSA-6626-79jh-5ccr
- web https://github.com/advisories/GHSA-9pq7-mfwh-xx2j