← Back
CVE-2026-46721
Vulnerability in evoweb/sf-register (CVE-2026-46721)
Summary
vulnerability in evoweb/sf-register (CVE-2026-46721). Risk of unauthorized operations or information disclosure. Exploitable via ``create``. Mitigation: upgrade to `13.2.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-46721** has been found in evoweb/sf-register.
Attackers can target a specific entry point like ``create`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade evoweb/sf-register to **13.2.4** or later.
If unsure, ask your IT team or search "evoweb/sf-register CVE-2026-46721" on the vendor's site.
CVE-2026-46721 (evoweb/sf-register) — CWE-639 /
Attack surface: `create` / `edit`
Patched: `13.2.4` — 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-639) exists in evoweb/sf-register. Attackers reach the vulnerable code path via ``create`` without authentication.
📍 Affected scope
evoweb/sf-register — . Attack surface: `create` / `edit`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **13.2.4**.
🛡️ 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 request patterns matching this CVE's known IOCs. Run `grep -r 'evoweb/sf-register' .` 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
-
1Identify exposure identify
grep -r 'evoweb/sf-register' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `evoweb/sf-register` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade evoweb/sf-register to 13.2.4ステージング環境で 13.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
evoweb/sf-register
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2.4"}]}]