← Back
CVE-2026-55372

SSRF (Server-Side Request Forgery) in nukeviet/nukeviet (CVE-2026-55372)

Summary

SSRF in nukeviet/nukeviet (CVE-2026-55372). Risk of unauthorized operations or information disclosure. Exploitable via `POST /index.php`. Mitigation: upgrade to `4.6.00` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-55372** has been found in nukeviet/nukeviet. Attackers can target a specific entry point like `POST /index.php` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade nukeviet/nukeviet to **4.6.00** or later. If unsure, ask your IT team or search "nukeviet/nukeviet CVE-2026-55372" on the vendor's site.
CVE-2026-55372 (nukeviet/nukeviet) — CWE-918 / Attack surface: POST /index.php / `POST` / `original_host` / `original_protocol` Patched: `4.6.00` — apply immediately Workaround: Configure the reverse proxy / web server to strip or override client-supplied `X-Forwarded-Host`, `X-Forwarded-Proto`, and `X-Forwarded-Port` headers, and ensure `my_domains` is configured with the site's canonical domain(s). 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
**SSRF** (CWE-918) exists in nukeviet/nukeviet. Attackers reach the vulnerable code path via `POST /index.php` without authentication.
📍 Affected scope
nukeviet/nukeviet — . Attack surface: POST /index.php / `POST` / `original_host` / `original_protocol`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.6.00**.
🛡️ Workaround
Workaround: Configure the reverse proxy / web server to strip or override client-supplied `X-Forwarded-Host`, `X-Forwarded-Proto`, and `X-Forwarded-Port` headers, and ensure `my_domains` is configured with the site's canonical domain(s).
🔍 Detection
Search webserver/proxy logs for unusual `POST /index.php` requests with malformed payloads or SQL meta-characters. Run `grep -r 'nukeviet/nukeviet' .` 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 'nukeviet/nukeviet' . | grep -v node_modules

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

  2. 3
    Hunt for indicators of compromise detect
    grep 'POST /index.php' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

  3. 5
    Apply temporary workaround mitigate
    Configure the reverse proxy / web server to strip or override client-supplied `X-Forwarded-Host`, `X-Forwarded-Proto`, and `X-Forwarded-Port` headers, and ensure `my_domains` is configured with the site's canonical domain(s).

    パッチが適用されるまでの応急処置として、Configure the reverse proxy / web server to strip or override client-supplied `X-Forwarded-Host`, `X-Forwarded-Proto`, and `X-Forwarded-Port` headers, and ensure `my_domains` is configured with the site's canonical domain(s). を実施。回避策の副作用 (機能低下) を確認した上で。

  4. 6
    Apply patch patch
    Upgrade nukeviet/nukeviet to 4.6.00

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

  5. 7
    Post-deployment verification verify
    Replay attack against POST /index.php on staging to confirm patch closes the vector

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

Affected packages

composer nukeviet/nukeviet
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.6.00"}]}]

References

🍪 About cookies

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

Details →