# Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS Advisory record · `GHSA-m5vr-3m74-jwxp` - **Identifiers:** `GHSA-m5vr-3m74-jwxp` · `BIT-typo3-2020-15098` · `CVE-2020-15098` · `PKSA-89kh-571y-53vr` · `PKSA-d1gc-jvn6-g46m` - **State:** Confirmed - **Severity:** CVSS 8.8 High - **Critical:** No - **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-325](https://cwe.mitre.org/data/definitions/325.html) · [CWE-327](https://cwe.mitre.org/data/definitions/327.html) · [CWE-502](https://cwe.mitre.org/data/definitions/502.html) - **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md) · [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md) · [CWE-325](https://agentprime.io/advisories/tag/cwe-325.md) - **Published:** 29 Jul 2020 - **Updated:** 8 Jul 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 29 Jul 2020, 16:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `typo3/cms-core` (Packagist): affected `>=9.0.0, <9.5.20 || >=10.0.0, <10.4.6`; fixed in `9.5.20`, `10.4.6` - `typo3/cms` (Packagist): affected `>=10.0.0, <10.4.6 || >=9.0.0, <9.5.20`; fixed in `10.4.6`, `9.5.20` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Affected versions of typo3/cms-core and typo3/cms are 9.0.0 up to but not including 9.5.20, and 10.0.0 up to but not including 10.4.6. An attacker who can use an internal verification mechanism to create valid HMAC-SHA1 checksums can inject arbitrary data, which can lead to privilege escalation or remote code execution in some attack chains; the attacker needs a valid backend user session or access to an Extbase plugin or module action, depending on the chain. Upgrade to typo3/cms-core or typo3/cms 9.5.20 or 10.4.6. Written 3 Nov 2026. ## 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 - 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.022, the 82nd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:25 UTC: First seen by agentprime - 31 Oct 2026, 14:25 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m5vr-3m74-jwxp) ## Sources - [GitHub Advisory Database: GHSA-m5vr-3m74-jwxp](https://github.com/advisories/GHSA-m5vr-3m74-jwxp) - [OSV: GHSA-m5vr-3m74-jwxp](https://osv.dev/vulnerability/GHSA-m5vr-3m74-jwxp) - - - - - - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .