# CVE-2022-44543: TYPO3 Extension femanager vulnerable to Broken Access Control

> Attackers can create frontend users in restricted groups by bypassing usergroup protection, leading to privilege escalation in TYPO3 installations.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Dec 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-59m9-p6cm-94q5

## What is CVE-2022-44543?

CVE-2022-44543 is a medium-severity vulnerability in n/a, published on 12 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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.

## Which versions are affected by CVE-2022-44543?

6 open source packages ship an affected version, including in2code/femanager. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `in2code/femanager` | Packagist | All versions | 5.5.2 |
| `in2code/femanager` | Packagist | All versions | 5.5.2 |
| `in2code/femanager` | Packagist | From 6.0.0 | 6.3.3 |
| `in2code/femanager` | Packagist | From 6.0.0 | 6.3.3 |
| `in2code/femanager` | Packagist | From 7.0.0 | 7.0.1 |
| `in2code/femanager` | Packagist | From 7.0.0 | 7.0.1 |

Products: In2code Femanager.

## How do I fix CVE-2022-44543?

Upgrade in2code/femanager to a fixed version for your release line: 5.5.2, 6.3.3 or 7.0.1.

## Is CVE-2022-44543 being exploited?

There is no known exploitation of CVE-2022-44543 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-25013](https://insights.sbomify.com/CVE-2023-25013/): Broken Access Control in 3rd party TYPO3 extension "femanager" (high 8.6)
- [CVE-2023-25014](https://insights.sbomify.com/CVE-2023-25014/): Broken Access Control in 3rd party TYPO3 extension "femanager" (high 8.6)
- [CVE-2014-6292](https://insights.sbomify.com/CVE-2014-6292/): TYPO3 femanager extension allows remote frontend users to modify or delete records of other frontend users (medium 6.4)
- [CVE-2021-36787](https://insights.sbomify.com/CVE-2021-36787/): Cross-site Scripting in the femanager TYPO3 extension (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-44543 and fix it if it is affected.

What it is: CVE-2022-44543 is a medium-severity vulnerability in n/a, published on 12 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-44543 in the wild and no public exploit code.

Affected packages and fixed versions:
- in2code/femanager (Packagist): affected all versions; fixed in 5.5.2
- in2code/femanager (Packagist): affected all versions; fixed in 5.5.2
- in2code/femanager (Packagist): affected from 6.0.0; fixed in 6.3.3
- in2code/femanager (Packagist): affected from 6.0.0; fixed in 6.3.3
- in2code/femanager (Packagist): affected from 7.0.0; fixed in 7.0.1
- in2code/femanager (Packagist): affected from 7.0.0; fixed in 7.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-44543/ (Markdown: https://insights.sbomify.com/CVE-2022-44543/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-44543
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-44543
- OSV: https://osv.dev/vulnerability/CVE-2022-44543

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-44543/
Summaries are generated and may contain mistakes; the official description above is the record.