Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-45701

Vulnerability in sulu/sulu (CVE-2026-45701)

Summary

Vulnerability in sulu/sulu (CVE-2026-45701). Risk of unauthorized operations or information disclosure. Exploitable via User.php. Mitigation: upgrade to 2.6.23 or later.

Original description

The description as published by the source.

Impact

The password reset tokenand API key generation uses a weak cryptographical hash algorithm.

Patches

Fixed in 2.6.23 and 3.0.6 version.

Workarounds

Patch the related User.php and ResettingController.php file in the SecurityBundle.

Source: GitHub Security Advisories (Global) 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-45701 has been found in sulu/sulu.
Attackers can target a specific entry point like User.php over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade sulu/sulu to 2.6.23 or later.
If unsure, ask your IT team or search "sulu/sulu CVE-2026-45701" on the vendor's site.

CVE-2026-45701 (sulu/sulu) — CWE-327
Attack surface: User.php / ResettingController.php
Patched: 2.6.23 — apply immediately
Workaround: Patch the related User.php and ResettingController.php file in the SecurityBundle.
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-327) exists in sulu/sulu. Attackers reach the vulnerable code path via User.php.

📍 Affected scope

Check the vendor advisory for the affected versions of sulu/sulu. Attack surface: User.php / ResettingController.php.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.6.23.

🛡️ Workaround

Workaround: Patch the related User.php and ResettingController.php file in the SecurityBundle.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'sulu/sulu' . 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

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

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

  2. 2
    Apply temporary workaround mitigate 
    Patch the related `User.php` and `ResettingController.php` file in the SecurityBundle.

    パッチが適用されるまでの応急処置として、Patch the related User.php and ResettingController.php file in the SecurityBundle. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade sulu/sulu to 2.6.23

    ステージング環境で 2.6.23 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

composer sulu/sulu
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.23"}]}]
Packagist sulu/sulu
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.23"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details