phpMyFAQ SQL injections at insertentry & saveentry
Summary
SQL injection reported (CVE-2024-28107). Successful exploitation can lead to full system takeover. Exploitable via insertentry. 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. A SQL injection vulnerability has been discovered in the insertentry & saveentry when modifying records due to improper escaping of the email address. This allows any authenticated user with the rights to add/edit FAQ news to exploit this vulnerability to exfiltrate data, take over accounts and in some cases, even achieve RCE. 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-28107 has been found.
Attackers can target a specific entry point like insertentry over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade the affected software to 3.2.6 or later.
If unsure, ask your IT team or search "CVE-2024-28107" on the vendor's site.
CVE-2024-28107 — CWE-89
Attack vector: remote (network-reachable) / no user interaction
Attack surface: insertentry / saveentry
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.
SQL injection (CWE-89) has been reported. Attackers reach the vulnerable code path via insertentry.
Check the vendor advisory for the affected versions. Attack surface: insertentry / saveentry.
Severity: ?. Successful exploitation can lead to full system takeover.
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