Vulnerability in thorsten/phpmyfaq (CVE-2026-48488)
Summary
Vulnerability in thorsten/phpmyfaq (CVE-2026-48488). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.1.4 or later.
Original description
The description as published by the source.
Summary
Attachment passwords are hashed using SHA-1, a cryptographically broken algorithm. SHA-1 has been vulnerable to collision attacks since 2017 (SHAttered).
Details
Affected File : phpmyfaq/src/phpMyFAQ/Attachment/AbstractAttachment.php
Impact
- An attacker can generate SHA-1 collisions to bypass attachment protection
- Risk of password cracking if database is compromised
- Estimated cracking time: < 1 minute for standard attachment
Solution
Use bcrypt:
public function setPassword(string $password): void
{
$this->passwordHash = password_hash($password, PASSWORD_BCRYPT);
}
public function verifyPassword(string $plainPassword): bool
{
return password_verify($plainPassword, $this->passwordHash);
}
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-48488 has been found in thorsten/phpmyfaq.
Risk of unauthorized operations or information disclosure.
What to do: upgrade thorsten/phpmyfaq to 4.1.4 or later.
If unsure, ask your IT team or search "thorsten/phpmyfaq CVE-2026-48488" on the vendor's site.
CVE-2026-48488 (thorsten/phpmyfaq) — CWE-328
Patched: 4.1.4 — 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-328) exists in thorsten/phpmyfaq.
Check the vendor advisory for the affected versions of thorsten/phpmyfaq.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.1.4.
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 '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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade thorsten/phpmyfaq to 4.1.4ステージング環境で 4.1.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com