# TYPO3 Scheduler Module vulnerable to Cross-Site Request Forgery

Advisory record · `GHSA-7835-fcv3-g256`

- **Identifiers:** `GHSA-7835-fcv3-g256` · `CVE-2024-55924` · `PKSA-vzxh-337v-pjvb`
- **State:** Confirmed
- **Severity:** CVSS 8.0 High
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html) · [CWE-749](https://cwe.mitre.org/data/definitions/749.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md) · [CWE-749](https://agentprime.io/advisories/tag/cwe-749.md)
- **Published:** 14 Jan 2025
- **Updated:** 21 May 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 Jan 2025, 15:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `typo3/cms-scheduler` (Packagist): affected `>=11.0.0, <11.5.42`; fixed in `11.5.42`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Affected: typo3/cms-scheduler from 11.0.0 before 11.5.42, fixed in 11.5.42. A cross-site request forgery flaw in the Scheduler Module lets an attacker trigger pre-defined backend commands, which can lead to unauthorized data import or export, if a logged-in backend user opens a malicious link or visits a compromised site with certain settings misconfigured. Upgrade to 11.5.42.

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.0 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0027, the 19th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:27 UTC: First seen by agentprime
- 31 Oct 2026, 14:27 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7835-fcv3-g256)

## Sources

- [GitHub Advisory Database: GHSA-7835-fcv3-g256](https://github.com/advisories/GHSA-7835-fcv3-g256)
- [OSV: GHSA-7835-fcv3-g256](https://osv.dev/vulnerability/GHSA-7835-fcv3-g256)
- <https://github.com/TYPO3/typo3/security/advisories/GHSA-7835-fcv3-g256>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-55924>
- <https://github.com/TYPO3-CMS/scheduler>
- <https://typo3.org/security/advisory/typo3-core-sa-2025-009>

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-7835-fcv3-g256>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-7835-fcv3-g256/>. Everything for agents: <https://agentprime.io/llms.txt>.