# CVE-2022-36106: Missing check for expiration time of password reset token in TYPO3

> Attackers can use expired password reset links to take over TYPO3 backend user accounts due to missing expiration checks.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Sep 2022
- **Updated:** 23 Apr 2025
- **Also known as:** BIT-typo3-2022-36106, GHSA-5959-4x58-r8c2

## What is CVE-2022-36106?

CVE-2022-36106 is a medium-severity authentication bypass vulnerability in Typo3 Typo3, published on 13 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TYPO3 is an open source PHP based web content management system released under the GNU GPL. It has been discovered that the expiration time of a password reset link for TYPO3 backend users has never been evaluated. As a result, a password reset link could be used to perform a password reset even if the default expiry time of two hours has been exceeded. Update to TYPO3 version 10.4.32 or 11.5.16 that fix the problem. There are no known workarounds for this issue.

Weakness: CWE-287 (Improper Authentication)

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

9 open source packages ship an affected version, including typo3/cms, typo3 and typo3/cms-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 10.4.0 | 10.4.32 |
| `typo3/cms` | Packagist | From 10.4.0 | 10.4.32 |
| `typo3/cms` | Packagist | From 11.0.0 | 11.5.16 |
| `typo3/cms` | Packagist | From 11.0.0 | 11.5.16 |
| `typo3` | Bitnami | From 10.0.0 | 10.4.31, 11.5.15 |
| `typo3/cms-core` | Packagist | From 10.4.0 | 10.4.32 |
| `typo3/cms-core` | Packagist | From 10.4.0 | 10.4.32 |
| `typo3/cms-core` | Packagist | From 11.0.0 | 11.5.16 |
| `typo3/cms-core` | Packagist | From 11.0.0 | 11.5.16 |

Products: Typo3 Typo3.

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

Upgrade typo3/cms to a fixed version for your release line: 10.4.32 or 11.5.16.

## Is CVE-2022-36106 being exploited?

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

## Other vulnerabilities in Typo3 Typo3

- [CVE-2009-0258](https://insights.sbomify.com/CVE-2009-0258/): Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection (critical 10.0)
- [CVE-2011-3583](https://insights.sbomify.com/CVE-2011-3583/): Typo3 SQL injection due to faulty prepared statements (critical 9.8)
- [CVE-2011-4628](https://insights.sbomify.com/CVE-2011-4628/): Typo3 Authentication Bypass (critical 9.8)
- [CVE-2023-24814](https://insights.sbomify.com/CVE-2023-24814/): Persisted Cross-Site Scripting in Frontend Rendering in typo3 (high 8.8)
- [CVE-2021-41113](https://insights.sbomify.com/CVE-2021-41113/): Cross-Site-Request-Forgery in Backend URI Handling in Typo3 (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36106 is a medium-severity authentication bypass vulnerability in Typo3 Typo3, published on 13 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36106 in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 10.4.0; fixed in 10.4.32
- typo3/cms (Packagist): affected from 10.4.0; fixed in 10.4.32
- typo3/cms (Packagist): affected from 11.0.0; fixed in 11.5.16
- typo3/cms (Packagist): affected from 11.0.0; fixed in 11.5.16
- typo3 (Bitnami): affected from 10.0.0; fixed in 10.4.31, 11.5.15
- typo3/cms-core (Packagist): affected from 10.4.0; fixed in 10.4.32
- typo3/cms-core (Packagist): affected from 10.4.0; fixed in 10.4.32
- typo3/cms-core (Packagist): affected from 11.0.0; fixed in 11.5.16
- typo3/cms-core (Packagist): affected from 11.0.0; fixed in 11.5.16

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

## Sources

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

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