{"answers":{"affected":"2 open source packages ship an affected version, including causal/oidc.","exploited":"There is no known exploitation of CVE-2025-24856 in the wild and no public exploit code.","fix":"Upgrade causal/oidc to 4.0.0 or later.","what":"CVE-2025-24856 is a medium-severity vulnerability in TYPO3 oidc, published on 16 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-24856 and fix it if it is affected.\n\nWhat it is: CVE-2025-24856 is a medium-severity vulnerability in TYPO3 oidc, published on 16 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-24856 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- causal/oidc (Packagist): affected from 3.0.0; fixed in 4.0.0\n- causal/oidc (Packagist): affected from 3.0.0; fixed in 4.0.0\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-2025-24856/ (Markdown: https://insights.sbomify.com/CVE-2025-24856/index.md)","id":"CVE-2025-24856","markdown":"https://insights.sbomify.com/CVE-2025-24856/index.md","name":"CVE-2025-24856","record":{"aliases":["GHSA-hj78-p4h7-m5fv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"TYPO3 OIDC extension","requires_auth":"none","summary":"Attackers can hijack accounts by pre-registering with a victim's email before their first OIDC login, requiring specific IDP email return conditions.","user_interaction":"required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N/E:F/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-348","name":"Use of Less Trusted Source"}],"description":"An issue was discovered in the oidc (aka OpenID Connect Authentication) extension before 4.0.0 for TYPO3. The account linking logic allows a pre-hijacking attack, leading to Account Takeover. The attack can only be exploited if the following requirements are met: (1) an attacker can anticipate the e-mail address of the user, (2) an attacker can register a public frontend user account using that e-mail address before the user's first OIDC login, and (3) the IDP returns an email field containing the e-mail address of the user,","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":"TYPO3-EXT-SA-2025-001: Account Takeover in extension \"OpenID Connect Authentication\" (oidc)","id":"CVE-2025-24856","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2025-24857"},"packages":[{"ecosystem":"Packagist","fixed":["4.0.0"],"introduced":["3.0.0"],"last_affected":[],"package":"causal/oidc","purl":null,"source":"GHSA-hj78-p4h7-m5fv"},{"ecosystem":"Packagist","fixed":["4.0.0"],"introduced":["3.0.0"],"last_affected":[],"package":"causal/oidc","purl":"pkg:composer/causal/oidc","source":"GHSA-hj78-p4h7-m5fv"}],"prev":{"headline":"Use after free in libxslt","id":"CVE-2025-24855"},"products":["oidc"],"published":"2025-03-16","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-17","vendors":["TYPO3"]},"summary":"Attackers can hijack accounts by pre-registering with a victim's email before their first OIDC login, requiring specific IDP email return conditions.","url":"https://insights.sbomify.com/CVE-2025-24856/"}