{"items":[{"id":"NVI-00004147","kind":"vulnerability","title":"TYPO3 CMS vulnerable to Weak Authentication in Frontend Login","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-jfp7-79g7-89rf","CVE-2022-23501"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 8.7.49 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 9.5.38 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 10.4.33 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.20 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.1.1 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 10.4.33 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.20 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.1.1 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-2891516b49eab2ae7d0f3caa69a3d110"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-17T04:30:14.927Z","value":"5.9 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-96535cb8facb1a53faf55c963ffe2231"},{"kind":"CVSS","as_of":"2026-06-17T04:30:14.927Z","value":"6.5 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-96535cb8facb1a53faf55c963ffe2231"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.511%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.43569. Missing scores are unknown.","source_id":"sr-2891516b49eab2ae7d0f3caa69a3d110"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-59dc3f75c7f6c80500dabed09a6bc937","url":"https://github.com/advisories/GHSA-jfp7-79g7-89rf","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jfp7-79g7-89rf","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.441Z"},{"id":"sr-96535cb8facb1a53faf55c963ffe2231","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-23501","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2022-23501","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T23:14:11.506Z"},{"id":"sr-2891516b49eab2ae7d0f3caa69a3d110","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2022-23501","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:14:50.774Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 8.7.49"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.38"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.33"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.20"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.1.1"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.33"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.20"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.1.1"]}],"null_published_at":"2026-11-08T19:53:38.900Z","source_updated_at":"2023-12-06T01:01:58.775Z","source_disclosed_at":"2022-12-13T17:04:02.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:20.441Z"},{"id":"NVI-00004147","kind":"vulnerability","title":"TYPO3 CMS vulnerable to Weak Authentication in Frontend Login","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-jfp7-79g7-89rf","CVE-2022-23501"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 8.7.49 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 9.5.38 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 10.4.33 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.20 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.1.1 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 10.4.33 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.20 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.1.1 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-6036d0d2777c2a1544609029fa76f439"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-17T04:30:14.927Z","value":"5.9 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-96535cb8facb1a53faf55c963ffe2231"},{"kind":"CVSS","as_of":"2026-06-17T04:30:14.927Z","value":"6.5 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-96535cb8facb1a53faf55c963ffe2231"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.511%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.43583. Missing scores are unknown.","source_id":"sr-6036d0d2777c2a1544609029fa76f439"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-59dc3f75c7f6c80500dabed09a6bc937","url":"https://github.com/advisories/GHSA-jfp7-79g7-89rf","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jfp7-79g7-89rf","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.441Z"},{"id":"sr-96535cb8facb1a53faf55c963ffe2231","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-23501","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2022-23501","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T23:14:11.506Z"},{"id":"sr-6036d0d2777c2a1544609029fa76f439","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2022-23501","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 8.7.49"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.38"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.33"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.20"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.1.1"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.33"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.20"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.1.1"]}],"null_published_at":"2026-11-04T18:04:07.065Z","source_updated_at":"2023-12-06T01:01:58.775Z","source_disclosed_at":"2022-12-13T17:04:02.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:20.441Z"},{"id":"NVI-00004147","kind":"vulnerability","title":"TYPO3 CMS vulnerable to Weak Authentication in Frontend Login","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jfp7-79g7-89rf","CVE-2022-23501"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 8.7.49 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 9.5.38 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 10.4.33 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.20 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.1.1 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 10.4.33 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.20 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.1.1 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-6036d0d2777c2a1544609029fa76f439"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.511%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.43583. Missing scores are unknown.","source_id":"sr-6036d0d2777c2a1544609029fa76f439"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-59dc3f75c7f6c80500dabed09a6bc937","url":"https://github.com/advisories/GHSA-jfp7-79g7-89rf","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jfp7-79g7-89rf","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.441Z"},{"id":"sr-6036d0d2777c2a1544609029fa76f439","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2022-23501","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 8.7.49"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.38"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.33"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.20"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.1.1"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.33"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.20"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.1.1"]}],"null_published_at":"2026-11-01T01:45:38.533Z","source_updated_at":"2023-12-06T01:01:58.775Z","source_disclosed_at":"2022-12-13T17:04:02.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:20.441Z"},{"id":"NVI-00004147","kind":"vulnerability","title":"TYPO3 CMS vulnerable to Weak Authentication in Frontend Login","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jfp7-79g7-89rf","CVE-2022-23501"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 8.7.49 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 9.5.38 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 10.4.33 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.20 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.1.1 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 10.4.33 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.20 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.1.1 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-59dc3f75c7f6c80500dabed09a6bc937","url":"https://github.com/advisories/GHSA-jfp7-79g7-89rf","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jfp7-79g7-89rf","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.441Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 8.7.49"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.38"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.33"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.20"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.1.1"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.33"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.20"]},{"certainty":"source_listed","source_ids":["sr-59dc3f75c7f6c80500dabed09a6bc937"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nRestricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-013\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.1.1"]}],"null_published_at":"2026-10-31T22:12:52.630Z","source_updated_at":"2023-12-06T01:01:58.775Z","source_disclosed_at":"2022-12-13T17:04:02.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:20.441Z"}],"next_cursor":null,"snapshot_revision":"42594"}