FemanagerTYPO3 extension · In2code
CVE-2022-44543
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe femanager extension before 5.5.2, 6.x before 6.3.3, and 7.x before 7.0.1 for TYPO3 allows creation of frontend users in restricted groups (if there is a usergroup field on the registration form). This occurs because the usergroup.inList protection mechanism is mishandled.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe femanager TYPO3 extension before version 5.5.2/6.3.3/7.0.1 fails to properly enforce the usergroup.inList protection during frontend user registration, allowing attackers to manipulate the usergroup field to assign newly created users to restricted or privileged groups that should be protected from self-registration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FemanagerTYPO3 extension
< 5.5.2>= 6.0.0, < 6.3.3= 7.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify femanager extension versionLocate the femanager extension in your TYPO3 installation (typically in typo3conf/ext/femanager or via composer vendor) and read the version from ext_emconf.php or composer.jsonAffected if Installed version is less than 5.5.2, or greater than or equal to 6.0.0 but less than 6.3.3, or exactly 7.0.0
-
Confirm frontend user registration is activeCheck if the femanager plugin is configured on a frontend page or if createUser functionality is enabled in the extension configuration or TypoScript setupAffected if Frontend user registration using femanager is enabled and accessible
-
Verify usergroup.inList protection existsExamine the TYPO3 TSconfig or femanager extension configuration for the usergroup.inList setting that specifies which user groups are allowed during self-registrationAffected if usergroup.inList is not configured or does not properly restrict the groups that can be assigned
Your environment is affected if femanager version is within the vulnerable range AND frontend user registration is enabled AND the usergroup.inList protection is either missing or not properly enforced during registration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.5.26.3.3
Upgrade femanager extension to version 5.5.2, 6.3.3, or 7.0.1 or later to receive the fix for the mishandled usergroup.inList protection mechanism.
Upgrade to Femanager version 5.5.2, 6.3.3, or 7.0.1 (depending on your current major version line)
- Backup your TYPO3 installation and database before proceeding
- Update the Femanager extension using Composer (composer require friendsoftypo3/femanager:^5.5.2 for version 5.x, ^6.3.3 for version 6.x, or ^7.0.1 for version 7.x) or via the TYPO3 Extension Manager
- Clear all TYPO3 caches after the update
- Verify that frontend user registration still works correctly and that the usergroup.inList protection is functioning as expected
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Femanager
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44543 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-44543 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data