# TYPO3 CMS missing check for expiration time of password reset token for backend users

Advisory record · `GHSA-5959-4x58-r8c2`

- **Identifiers:** `GHSA-5959-4x58-r8c2` · `BIT-typo3-2022-36106` · `CVE-2022-36106` · `PKSA-v1kb-vbr1-8fy1` · `PKSA-z12b-qvn6-4p12`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 16 Sept 2022
- **Updated:** 6 Dec 2023
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 16 Sept 2022, 17:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `typo3/cms-core` (Packagist): affected `>=10.4.0, <10.4.32 || >=11.0.0, <11.5.16`; fixed in `10.4.32`, `11.5.16`
- `typo3/cms` (Packagist): affected `>=10.4.0, <10.4.32 || >=11.0.0, <11.5.16`; fixed in `10.4.32`, `11.5.16`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0097, the 62nd percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 16 Sept 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-5959-4x58-r8c2](https://github.com/advisories/GHSA-5959-4x58-r8c2)
- [OSV: GHSA-5959-4x58-r8c2](https://osv.dev/vulnerability/GHSA-5959-4x58-r8c2)
- <https://github.com/TYPO3/typo3/security/advisories/GHSA-5959-4x58-r8c2>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-36106>
- <https://github.com/TYPO3/typo3/commit/00b52a443b21baaaab35f8606dbb0ce427261bb5>
- <https://github.com/TYPO3/typo3/commit/56af2bd3a432156c30af9be71c9d6f7ef3a6159a>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2022-36106.yaml>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2022-36106.yaml>
- <https://github.com/TYPO3/typo3>
- <https://typo3.org/security/advisory/typo3-core-sa-2022-008>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-5959-4x58-r8c2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-5959-4x58-r8c2/>. Everything for agents: <https://agentprime.io/llms.txt>.
