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.
Original description
The description as published by the source.
The create and edit flows do not restrict which user properties may be submitted and do not enforce access control on the frontend user group assignment. As a result, an attacker can assign an arbitrary frontend user group to a newly registered or edited account, gaining unauthorized access to content and functionality restricted to privileged frontend user groups.
Source: NIST National Vulnerability Database 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-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.
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.
A vulnerability (CWE-639) exists in evoweb/sf-register. Attackers reach the vulnerable code path via create.
Check the vendor advisory for the affected versions of evoweb/sf-register. Attack surface: create / edit.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 13.2.4.
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. Run grep -r 'evoweb/sf-register' . 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
-
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade evoweb/sf-register to 13.2.4ステージング環境で 13.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory typo3.org
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web packagist.org