# CVE-2026-77133: Broken Access Control in extension "femanager" (femanager)

> Logged-in users can escalate privileges by assigning themselves to arbitrary frontend usergroups via the femanager extension's default profile edit configuration.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-qjph-66v6-w5fp

## What is CVE-2026-77133?

CVE-2026-77133 is a medium-severity vulnerability in TYPO3 Extension "femanager", published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The extension fails to restrict which frontend usergroups a logged-in user may assign to their own account when the profile edit plugin uses its default field configuration, allowing self-service privilege escalation into arbitrary frontend groups.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-77133?


## How do I fix CVE-2026-77133?

No fix has been published for CVE-2026-77133 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-77133 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77133 and fix it if it is affected.

What it is: CVE-2026-77133 is a medium-severity vulnerability in TYPO3 Extension "femanager", published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77133 in the wild and no public exploit code.

Affected product: TYPO3 Extension "femanager". No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2026-77133/ (Markdown: https://insights.sbomify.com/CVE-2026-77133/index.md)
```

## Sources

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

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