← Back
CVE-2026-46365 medium CVSS 5.4

Vulnerability in phpMyFAQ/phpMyFAQ (CVE-2026-46365)

Summary

vulnerability in phpMyFAQ/phpMyFAQ (CVE-2026-46365). Risk of unauthorized operations or information disclosure. Exploitable via `DELETE /admin/api/content/tags/{tagId}`. Mitigation: upgrade to `4.1.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-46365** has been found in phpMyFAQ/phpMyFAQ. Attackers can target a specific entry point like `DELETE /admin/api/content/tags/{tagId}` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10. What to do: upgrade phpMyFAQ/phpMyFAQ to **4.1.2** or later. If unsure, ask your IT team or search "phpMyFAQ/phpMyFAQ CVE-2026-46365" on the vendor's site.
CVE-2026-46365 (phpMyFAQ/phpMyFAQ) — CWE-862 / CVSS v3 5.4 Attack vector: remote (network-reachable) / no user interaction Attack surface: DELETE /admin/api/content/tags/{tagId} Patched: `4.1.2` — 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.
❓ What is the problem
**A vulnerability** (CWE-862) exists in phpMyFAQ/phpMyFAQ. Attackers reach the vulnerable code path via `DELETE /admin/api/content/tags/{tagId}` without authentication.
📍 Affected scope
phpMyFAQ/phpMyFAQ — . Attack surface: DELETE /admin/api/content/tags/{tagId}.
🔥 Severity
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.1.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `DELETE /admin/api/content/tags/{tagId}` requests with malformed payloads or SQL meta-characters. Run `grep -r 'phpMyFAQ/phpMyFAQ' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'phpMyFAQ/phpMyFAQ' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `phpMyFAQ/phpMyFAQ` を grep し、稼働しているサービス・バージョンを把握する。

  2. 3
    Hunt for indicators of compromise detect
    grep 'DELETE /admin/api/content/tags/{tagId}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで `DELETE /admin/api/content/tags/{tagId}` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 6
    Apply patch patch
    Upgrade phpMyFAQ/phpMyFAQ to 4.1.2

    ステージング環境で 4.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify
    Replay attack against DELETE /admin/api/content/tags/{tagId} on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

composer phpMyFAQ/phpMyFAQ
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.2"}]}]
composer thorsten/phpMyFAQ
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.2"}]}]
Packagist phpMyFAQ/phpMyFAQ
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.2"}]}]
Packagist thorsten/phpMyFAQ
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.2"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →