How severe is CVE-2026-46721?

No CVSS score has been assigned to CVE-2026-46721 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-46721?

CVE-2026-46721 affects the following packages: evoweb/sf-register (Packagist), evoweb/sf-register (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2026-46721?

Update evoweb/sf-register to 14.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-46721 is resolved across your whole dependency graph.

How do I detect CVE-2026-46721 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for evoweb/sf-register, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-46721 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-46721 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-46721 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-46721?

CVE-2026-46721 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-46721?

CVE-2026-46721 is classified as CWE-639 (CWE-639), CWE-915 (CWE-915). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-46721 published, and has it been updated?

CVE-2026-46721 was published on May 19, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2026-46721 — evoweb/sf-register

CVE-2026-46721 is a CWE-639 vulnerability in evoweb/sf-register. A fix is available for evoweb/sf-register — see the affected versions and patch details below.

Broken Access Control in extension "Frontend User Registration" (sf_register)

Also known asGHSA-v348-vr4q-fv9p

Published

May 19, 2026

Updated

Aug 12, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-46721.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk+0.08%

Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐘evoweb/sf-register🐘evoweb/sf-register

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`evoweb/sf-register`	≥ 14.0.0&&< 14.0.2	14.0.2`composer require evoweb/sf-register:^14.0.2`
🐘Packagist	`evoweb/sf-register`	all versions	13.2.4`composer require evoweb/sf-register:^13.2.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for evoweb/sf-register, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update evoweb/sf-register to 14.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-46721 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2026-46721 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works