{"answers":{"affected":"4 open source packages ship an affected version, including typo3/cms-core.","exploited":"There is no known exploitation of GHSA-rxc9-f2x6-qh4w in the wild and no public exploit code.","fix":"Upgrade typo3/cms-core to a fixed version for your release line: 8.7.23 or 9.5.4.","what":"GHSA-rxc9-f2x6-qh4w is a vulnerability in typo3/cms-core, published on 30 May 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for GHSA-rxc9-f2x6-qh4w and fix it if it is affected.\n\nWhat it is: GHSA-rxc9-f2x6-qh4w is a vulnerability in typo3/cms-core, published on 30 May 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-rxc9-f2x6-qh4w in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms-core (Packagist): affected from 8.0.0; fixed in 8.7.23\n- typo3/cms-core (Packagist): affected from 8.0.0; fixed in 8.7.23\n- typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.4\n- typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.4\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/GHSA-rxc9-f2x6-qh4w/ (Markdown: https://insights.sbomify.com/GHSA-rxc9-f2x6-qh4w/index.md)","id":"GHSA-rxc9-f2x6-qh4w","markdown":"https://insights.sbomify.com/GHSA-rxc9-f2x6-qh4w/index.md","name":"GHSA-rxc9-f2x6-qh4w","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 CMS","requires_auth":"high_privilege","summary":"TYPO3 backend allows creating user accounts with empty or weak credentials due to form reload logic, potentially enabling authentication bypass in custom implementations.","user_interaction":"required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"When using the TYPO3 backend in order to create new backend user accounts, database records containing insecure or empty credentials might be persisted. When the type of user account is changed - which might be entity type or the admin flag for backend users - the backend form is reloaded in order to reflect changed configuration possibilities. However,  this leads to persisting the current state as well, which can result into some of the following:\n\n- account contains empty login credentials (username and/or password)\n- account is incomplete and contains weak credentials (username and/or password)\n\nAlbeit the functionality provided by the TYPO3 core cannot be used either with empty usernames or empty passwords, it still can be a severe vulnerability to custom authentication service implementations.\n\nThis weakness cannot be directly exploited and requires interaction on purpose by some backend user having according privileges.","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"TYPO3 Security Misconfiguration for Backend User Accounts","id":"GHSA-rxc9-f2x6-qh4w","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"misconfiguration","year":"2024"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["8.7.23"],"introduced":["8.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-rxc9-f2x6-qh4w"},{"ecosystem":"Packagist","fixed":["8.7.23"],"introduced":["8.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-rxc9-f2x6-qh4w"},{"ecosystem":"Packagist","fixed":["9.5.4"],"introduced":["9.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-rxc9-f2x6-qh4w"},{"ecosystem":"Packagist","fixed":["9.5.4"],"introduced":["9.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-rxc9-f2x6-qh4w"}],"products":null,"published":"2024-05-30","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"TYPO3 backend allows creating user accounts with empty or weak credentials due to form reload logic, potentially enabling authentication bypass in custom implementations.","url":"https://insights.sbomify.com/GHSA-rxc9-f2x6-qh4w/"}