← Back
CVE-2026-45008
medium
CVSS 6.5
Path Traversal in phpMyFAQ/phpMyFAQ (CVE-2026-45008)
Summary
path traversal in phpMyFAQ/phpMyFAQ (CVE-2026-45008). Data can be tampered with by attackers. Exploitable via ``clientFolder``. Mitigation: upgrade to `4.1.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45008** has been found in phpMyFAQ/phpMyFAQ.
Attackers can target a specific entry point like ``clientFolder`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade phpMyFAQ/phpMyFAQ to **4.1.2** or later.
If unsure, ask your IT team or search "phpMyFAQ/phpMyFAQ CVE-2026-45008" on the vendor's site.
CVE-2026-45008 (phpMyFAQ/phpMyFAQ) — CWE-22 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `clientFolder` / `INSTANCE_DELETE` / `str_replace` / `admin.api.instance.delete`
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
**Path traversal** (CWE-22) exists in phpMyFAQ/phpMyFAQ. Attackers reach the vulnerable code path via ``clientFolder`` without authentication.
📍 Affected scope
phpMyFAQ/phpMyFAQ — . Attack surface: `clientFolder` / `INSTANCE_DELETE` / `str_replace` / `admin.api.instance.delete`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers
🔧 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 request patterns matching this CVE's known IOCs. Run `grep -r 'phpMyFAQ/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 'phpMyFAQ/phpMyFAQ' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `phpMyFAQ/phpMyFAQ` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade phpMyFAQ/phpMyFAQ to 4.1.2ステージング環境で 4.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
phpMyFAQ/phpMyFAQ
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.2"}]}]
Packagist
phpMyFAQ/phpMyFAQ
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.2"}]}]
composer
thorsten/phpmyfaq
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.2"}]}]
Packagist
thorsten/phpmyfaq
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-45008
- package https://github.com/thorsten/phpMyFAQ
- web https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-gh9p-q46p-57g2
- web https://www.vulncheck.com/advisories/phpmyfaq-path-traversal-in-client-deleteclientfolder-via-url-parameter
- web https://github.com/advisories/GHSA-rmqr-h98c-qg2m
- web https://github.com/advisories/GHSA-gh9p-q46p-57g2