packagist package report

Is evoweb/sf-register safe?

1 known vulnerability, worst severity MODERATE.

cvss
6.9

how bad it is if exploited, out of 10

epss
0.40%

chance of exploitation in the next 30 days

xyz score
not scored

CyberXYZ composite, out of 10

fig. 01 — GHSA-v348-vr4q-fv9p, the advisory selected below

// advisories

GHSA-v348-vr4q-fv9p

MODERATECVE-2026-46721

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

Affected
>= 14.0.0, < 14.0.2
Fixed in
14.0.2
Weakness
CWE-639
Published
2026-05-19
Source
github

GHSANVDMITREreferencereference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so packagist packages are not covered.

Checked 2026-09-22 at 02:41 UTC. The most recent advisory here was published 2026-05-19. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is evoweb/sf-register safe? packagist package security report | CyberXYZ