phpMyFAQ Stored HTML Injection at contentLink
Summary
Cross-site scripting reported (CVE-2024-28108). Risk of unauthorized operations or information disclosure. Exploitable via contentLink. Mitigation: upgrade to 3.2.6 or later.
Original description
The description as published by the source.
phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. Due to insufficient validation on the contentLink parameter, it is possible for unauthenticated users to inject HTML code to the page which might affect other users. Also, requires that adding new FAQs is allowed for guests and that the admin doesn't check the content of a newly added FAQ. This vulnerability is fixed in 3.2.6.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-2024-28108 has been found.
Attackers can target a specific entry point like contentLink over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade the affected software to 3.2.6 or later.
If unsure, ask your IT team or search "CVE-2024-28108" on the vendor's site.
CVE-2024-28108 — CWE-79
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: contentLink
Patched: 3.2.6 — 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.
Cross-site scripting (XSS) (CWE-79) has been reported. Attackers reach the vulnerable code path via contentLink without authentication.
Check the vendor advisory for the affected versions. Attack surface: contentLink.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.2.6.
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. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Apply patch patch
Upgrade to 3.2.6ステージング環境で 3.2.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com