# CVE-2023-25013: Broken Access Control in 3rd party TYPO3 extension "femanager"

> Unauthenticated attackers can reset passwords for all frontend users due to missing access checks in the TYPO3 femanager extension.

- **Severity:** High 8.6 (`CVSS:3.1/AC:L/AV:N/A:L/C:L/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Feb 2023
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-mm8v-wmqx-8h2j

## What is CVE-2023-25013?

CVE-2023-25013 is a high-severity missing authorization vulnerability in n/a, published on 2 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the femanager extension before 5.5.3, 6.x before 6.3.4, and 7.x before 7.1.0 for TYPO3. Missing access checks in the InvitationController allow an unauthenticated user to set the password of all frontend users.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2023-25013?

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.3 |
| `in2code/femanager` | Packagist | All versions | 5.5.3 |
| `in2code/femanager` | Packagist | From 6.0.0 | 6.3.4 |
| `in2code/femanager` | Packagist | From 6.0.0 | 6.3.4 |
| `in2code/femanager` | Packagist | From 7.0.0 | 7.1.0 |
| `in2code/femanager` | Packagist | From 7.0.0 | 7.1.0 |

Products: In2code Femanager.

## How do I fix CVE-2023-25013?

Upgrade in2code/femanager to a fixed version for your release line: 5.5.3, 6.3.4 or 7.1.0.

## Is CVE-2023-25013 being exploited?

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

## Other vulnerabilities in n/a

- [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)
- [CVE-2022-44543](https://insights.sbomify.com/CVE-2022-44543/): TYPO3 Extension femanager vulnerable to Broken Access Control (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25013 and fix it if it is affected.

What it is: CVE-2023-25013 is a high-severity missing authorization vulnerability in n/a, published on 2 Feb 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-2023-25013 in the wild and no public exploit code.

Affected packages and fixed versions:
- in2code/femanager (Packagist): affected all versions; fixed in 5.5.3
- in2code/femanager (Packagist): affected all versions; fixed in 5.5.3
- in2code/femanager (Packagist): affected from 6.0.0; fixed in 6.3.4
- in2code/femanager (Packagist): affected from 6.0.0; fixed in 6.3.4
- in2code/femanager (Packagist): affected from 7.0.0; fixed in 7.1.0
- in2code/femanager (Packagist): affected from 7.0.0; fixed in 7.1.0

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

## Sources

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

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