Vulnerability in thorsten/phpmyfaq (CVE-2026-35676)
Summary
Vulnerability in thorsten/phpmyfaq (CVE-2026-35676). Data can be tampered with by attackers. Exploitable via PUT /api/index.php/user/password/update. Mitigation: upgrade to 4.1.3 or later.
Original description
The description as published by the source.
phpMyFAQ before 4.1.3 contains an unauthenticated password reset vulnerability in the user password update API endpoint that allows attackers to change account passwords without token validation. Attackers can enumerate valid username and email pairs and force immediate password changes by sending PUT requests to the /api/index.php/user/password/update endpoint, causing account disruption and invalidating legitimate user credentials.
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-35676 has been found in thorsten/phpmyfaq.
Attackers can target a specific entry point like PUT /api/index.php/user/password/update over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.2/10.
What to do: upgrade thorsten/phpmyfaq to 4.1.3 or later.
If unsure, ask your IT team or search "thorsten/phpmyfaq CVE-2026-35676" on the vendor's site.
CVE-2026-35676 (thorsten/phpmyfaq) — CWE-640 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: PUT /api/index.php/user/password/update / POST /authenticate / user2 / faquserlogin
Patched: 4.1.3 — 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-640) exists in thorsten/phpmyfaq. Attackers reach the vulnerable code path via PUT /api/index.php/user/password/update without authentication.
Check the vendor advisory for the affected versions of thorsten/phpmyfaq. Attack surface: PUT /api/index.php/user/password/update / POST /authenticate / user2 / faquserlogin.
Severity: High (CVSS 8.2/10). Data can be tampered with by attackers.
Update to 4.1.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PUT /api/index.php/user/password/update 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 'PUT /api/index.php/user/password/update' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PUT /api/index.php/user/password/updateへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade thorsten/phpmyfaq to 4.1.3ステージング環境で 4.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against PUT /api/index.php/user/password/update on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory vulncheck.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com