What is CVE-2026-46721?

CVE-2026-46721 is a medium-severity security vulnerability in evoweb/sf-register (composer), affecting versions >= 14.0.0, < 14.0.2. It is fixed in 14.0.2, 13.2.4.

Which versions of evoweb/sf-register are affected by CVE-2026-46721?

evoweb/sf-register (composer) versions >= 14.0.0, < 14.0.2 is affected.

Is there a fix for CVE-2026-46721?

Yes. CVE-2026-46721 is fixed in 14.0.2, 13.2.4. Upgrade to this version or later.

Is CVE-2026-46721 exploitable, and should I be worried?

Whether CVE-2026-46721 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-46721 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-46721 in evoweb/sf-register

Q: Which versions of evoweb/sf-register are affected by CVE-2026-46721?

evoweb/sf-register (composer) versions >= 14.0.0, < 14.0.2 is affected.

Q: Is there a fix for CVE-2026-46721?

Yes. CVE-2026-46721 is fixed in 14.0.2, 13.2.4. Upgrade to this version or later.

Q: Is CVE-2026-46721 exploitable, and should I be worried?

Whether CVE-2026-46721 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-46721 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-46721?

Upgrade: evoweb/sf-register to 14.0.2 or later, evoweb/sf-register to 13.2.4 or later.

Summary

TYPO3 sf_register extension allows unauthorized assignment of frontend user groups

The create and edit flows in the TYPO3 extension sf_register 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.

Impact

Affected versions

evoweb/sf-register (>= 14.0.0, < 14.0.2) evoweb/sf-register (< 13.2.4)

Security releases

evoweb/sf-register → 14.0.2 (composer) evoweb/sf-register → 13.2.4 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

evoweb/sf-register to 14.0.2 or later; evoweb/sf-register to 13.2.4 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-46721? CVE-2026-46721 is a medium-severity security vulnerability in evoweb/sf-register (composer), affecting versions >= 14.0.0, < 14.0.2. It is fixed in 14.0.2, 13.2.4.
Which versions of evoweb/sf-register are affected by CVE-2026-46721? evoweb/sf-register (composer) versions >= 14.0.0, < 14.0.2 is affected.
Is there a fix for CVE-2026-46721? Yes. CVE-2026-46721 is fixed in 14.0.2, 13.2.4. Upgrade to this version or later.
Is CVE-2026-46721 exploitable, and should I be worried? Whether CVE-2026-46721 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-46721 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-46721?
- Upgrade evoweb/sf-register to 14.0.2 or later
- Upgrade evoweb/sf-register to 13.2.4 or later