Vulnerability in phpMyFAQ (CVE-2026-76208)
Summary
Vulnerability in phpMyFAQ (CVE-2026-76208). Data can be tampered with by attackers. Mitigation: upgrade to 4.1.7 or later.
Original description
The description as published by the source.
phpMyFAQ versions 3.1.0 through 4.1.6 contain an authentication bypass vulnerability in AuthLdap::create(). When LDAP authentication is enabled, after a successful LDAP bind the code calls User::setStatus('active') unconditionally, which overwrites the account_status column of a pre-existing local account from 'blocked' to 'active'. As a result, a user whose local phpMyFAQ account has been administratively blocked can restore their account and log in by authenticating via LDAP. The state transition is not logged, so administrators cannot detect that the block was overridden. Fixed in 4.1.7.
Source: NIST National Vulnerability Database 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-76208 has been found in phpMyFAQ.
Data can be tampered with by attackers. CVSS score: 8.2/10.
What to do: upgrade phpMyFAQ to 4.1.7 or later.
If unsure, ask your IT team or search "phpMyFAQ CVE-2026-76208" on the vendor's site.
CVE-2026-76208 (phpMyFAQ) — CWE-778 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.1.7 — 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-778) exists in phpMyFAQ.
Check the vendor advisory for the affected versions of phpMyFAQ.
Severity: High (CVSS 8.2/10). Data can be tampered with by attackers.
Update to 4.1.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '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 'phpMyFAQ' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
phpMyFAQを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade phpMyFAQ to 4.1.7ステージング環境で 4.1.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory disclosure@vulncheck.com
- exploit github.com
- web nvd.nist.gov
- web github.com