{"answers":{"affected":"2 open source packages ship an affected version, including typo3/cms-scheduler. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-55924 in the wild and no public exploit code.","fix":"Upgrade typo3/cms-scheduler to 11.5.42 or later.","what":"CVE-2024-55924 is a high-severity vulnerability in Typo3 Typo3, published on 14 Jan 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-55924 and fix it if it is affected.\n\nWhat it is: CVE-2024-55924 is a high-severity vulnerability in Typo3 Typo3, published on 14 Jan 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-55924 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms-scheduler (Packagist): affected from 11.0.0; fixed in 11.5.42\n- typo3/cms-scheduler (Packagist): affected from 11.0.0; fixed in 11.5.42\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-55924/ (Markdown: https://insights.sbomify.com/CVE-2024-55924/index.md)","id":"CVE-2024-55924","markdown":"https://insights.sbomify.com/CVE-2024-55924/index.md","name":"CVE-2024-55924","record":{"aliases":["GHSA-7835-fcv3-g256"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"TYPO3 Scheduler Module","requires_auth":"low_privilege","summary":"Attackers can trigger unauthorized data import or export via CSRF in the TYPO3 Scheduler Module if specific security settings are misconfigured.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"typo3","vendor":"typo3"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-749","name":"Exposed Dangerous Method or Function"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"TYPO3 is a free and open source Content Management Framework. A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in downstream components incorrectly accepted submissions via HTTP GET and did not enforce the appropriate HTTP method. Successful exploitation of this vulnerability requires the victim to have an active session on the backend user interface and to be deceived into interacting with a malicious URL targeting the backend, which can occur under the following conditions: The user opens a malicious link, such as one sent via email. The user visits a compromised or manipulated website while the following settings are misconfigured: 1. `security.backend.enforceReferrer` feature is disabled, 2. `BE/cookieSameSite` configuration is set to lax or none. The vulnerability in the affected downstream component “Scheduler Module” allows attackers to trigger pre-defined command classes - which can lead to unauthorized import or export of data in the worst case. Users are advised to update to TYPO3 versions 11.5.42 ELTS which fixes the problem described. There are no known workarounds for this vulnerability.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Cross-Site Request Forgery in Scheduler Module in TYPO3","id":"CVE-2024-55924","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"typo3:typo3","products":["typo3:typo3"],"type":"csrf","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"API Security bypass through header manipulation","id":"CVE-2024-55925"},"packages":[{"ecosystem":"Packagist","fixed":["11.5.42"],"introduced":["11.0.0"],"last_affected":[],"package":"typo3/cms-scheduler","purl":null,"source":"GHSA-7835-fcv3-g256"},{"ecosystem":"Packagist","fixed":["11.5.42"],"introduced":["11.0.0"],"last_affected":[],"package":"typo3/cms-scheduler","purl":"pkg:composer/typo3/cms-scheduler","source":"GHSA-7835-fcv3-g256"}],"prev":{"headline":"Cross-Site Request Forgery in Indexed Search Module in TYPO3","id":"CVE-2024-55923"},"products":["typo3"],"published":"2025-01-14","related":[{"cvss_score":10,"headline":"Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection","id":"CVE-2009-0258","kev_date_added":null,"published":"2009-01-22"},{"cvss_score":9.8,"headline":"Typo3 SQL injection due to faulty prepared statements","id":"CVE-2011-3583","kev_date_added":null,"published":"2019-11-25"},{"cvss_score":9.8,"headline":"Typo3 Authentication Bypass","id":"CVE-2011-4628","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":8.8,"headline":"Persisted Cross-Site Scripting in Frontend Rendering in typo3","id":"CVE-2023-24814","kev_date_added":null,"published":"2023-02-07"},{"cvss_score":8.8,"headline":"Cross-Site-Request-Forgery in Backend URI Handling in Typo3","id":"CVE-2021-41113","kev_date_added":null,"published":"2021-10-05"},{"cvss_score":8.8,"headline":"Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS","id":"CVE-2020-15098","kev_date_added":null,"published":"2020-07-29"},{"cvss_score":8.8,"headline":"Deserialization of Untrusted Data in TYPO3 CMS","id":"CVE-2020-11067","kev_date_added":null,"published":"2020-05-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-15","vendors":["TYPO3"]},"summary":"Attackers can trigger unauthorized data import or export via CSRF in the TYPO3 Scheduler Module if specific security settings are misconfigured.","url":"https://insights.sbomify.com/CVE-2024-55924/"}