{"items":[{"id":"NVI-00007999","kind":"vulnerability","title":"TYPO3 CMS vulnerable to User Enumeration via Response Timing","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-m392-235j-9r7r","CVE-2022-36105"],"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 7.6.58 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"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 8.7.48 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"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.37 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"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.32 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"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.16 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"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.32 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"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.16 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"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-70573e09e0da62910e9429d537802c3c"],"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":"1.261%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.69643. Missing scores are unknown.","source_id":"sr-70573e09e0da62910e9429d537802c3c"}],"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-f1ced0489e02b6b1185b548289d0f9e9","url":"https://github.com/advisories/GHSA-m392-235j-9r7r","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m392-235j-9r7r","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.972Z"},{"id":"sr-70573e09e0da62910e9429d537802c3c","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-36105","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (4.9)\n\n### Problem\nIt has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.\n\nExtension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new `MimicServiceInterface::mimicAuthUser`, which simulates corresponding times regular processing would usually take.\n\n### Solution\nUpdate to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.\n\n### Credits\nThanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2022-007\n* Vulnerability Report on huntr.dev (embargoed +30 days)","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.6.58"]},{"certainty":"source_listed","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (4.9)\n\n### Problem\nIt has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.\n\nExtension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new `MimicServiceInterface::mimicAuthUser`, which simulates corresponding times regular processing would usually take.\n\n### Solution\nUpdate to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.\n\n### Credits\nThanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2022-007\n* Vulnerability Report on huntr.dev (embargoed +30 days)","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.48"]},{"certainty":"source_listed","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (4.9)\n\n### Problem\nIt has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.\n\nExtension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new `MimicServiceInterface::mimicAuthUser`, which simulates corresponding times regular processing would usually take.\n\n### Solution\nUpdate to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.\n\n### Credits\nThanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2022-007\n* Vulnerability Report on huntr.dev (embargoed +30 days)","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.37"]},{"certainty":"source_listed","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (4.9)\n\n### Problem\nIt has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.\n\nExtension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new `MimicServiceInterface::mimicAuthUser`, which simulates corresponding times regular processing would usually take.\n\n### Solution\nUpdate to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.\n\n### Credits\nThanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2022-007\n* Vulnerability Report on huntr.dev (embargoed +30 days)","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.32"]},{"certainty":"source_listed","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (4.9)\n\n### Problem\nIt has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.\n\nExtension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new `MimicServiceInterface::mimicAuthUser`, which simulates corresponding times regular processing would usually take.\n\n### Solution\nUpdate to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.\n\n### Credits\nThanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2022-007\n* Vulnerability Report on huntr.dev (embargoed +30 days)","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.16"]},{"certainty":"source_listed","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (4.9)\n\n### Problem\nIt has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.\n\nExtension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new `MimicServiceInterface::mimicAuthUser`, which simulates corresponding times regular processing would usually take.\n\n### Solution\nUpdate to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.\n\n### Credits\nThanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2022-007\n* Vulnerability Report on huntr.dev (embargoed +30 days)","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.32"]},{"certainty":"source_listed","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (4.9)\n\n### Problem\nIt has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.\n\nExtension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new `MimicServiceInterface::mimicAuthUser`, which simulates corresponding times regular processing would usually take.\n\n### Solution\nUpdate to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.\n\n### Credits\nThanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2022-007\n* Vulnerability Report on huntr.dev (embargoed +30 days)","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.16"]}],"null_published_at":"2026-11-01T19:14:01.586Z","source_updated_at":"2023-12-06T01:02:29.779Z","source_disclosed_at":"2022-09-16T17:16:28.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:30.972Z"},{"id":"NVI-00007999","kind":"vulnerability","title":"TYPO3 CMS vulnerable to User Enumeration via Response Timing","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-m392-235j-9r7r","CVE-2022-36105"],"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 7.6.58 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"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 8.7.48 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"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.37 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"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.32 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"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.16 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"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.32 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"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.16 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"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-f1ced0489e02b6b1185b548289d0f9e9","url":"https://github.com/advisories/GHSA-m392-235j-9r7r","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m392-235j-9r7r","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.972Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (4.9)\n\n### Problem\nIt has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.\n\nExtension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new `MimicServiceInterface::mimicAuthUser`, which simulates corresponding times regular processing would usually take.\n\n### Solution\nUpdate to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.\n\n### Credits\nThanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2022-007\n* Vulnerability Report on huntr.dev (embargoed +30 days)","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.6.58"]},{"certainty":"source_listed","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (4.9)\n\n### Problem\nIt has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.\n\nExtension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new `MimicServiceInterface::mimicAuthUser`, which simulates corresponding times regular processing would usually take.\n\n### Solution\nUpdate to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.\n\n### Credits\nThanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2022-007\n* Vulnerability Report on huntr.dev (embargoed +30 days)","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.48"]},{"certainty":"source_listed","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (4.9)\n\n### Problem\nIt has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.\n\nExtension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new `MimicServiceInterface::mimicAuthUser`, which simulates corresponding times regular processing would usually take.\n\n### Solution\nUpdate to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.\n\n### Credits\nThanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2022-007\n* Vulnerability Report on huntr.dev (embargoed +30 days)","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.37"]},{"certainty":"source_listed","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (4.9)\n\n### Problem\nIt has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.\n\nExtension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new `MimicServiceInterface::mimicAuthUser`, which simulates corresponding times regular processing would usually take.\n\n### Solution\nUpdate to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.\n\n### Credits\nThanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2022-007\n* Vulnerability Report on huntr.dev (embargoed +30 days)","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.32"]},{"certainty":"source_listed","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (4.9)\n\n### Problem\nIt has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.\n\nExtension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new `MimicServiceInterface::mimicAuthUser`, which simulates corresponding times regular processing would usually take.\n\n### Solution\nUpdate to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.\n\n### Credits\nThanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2022-007\n* Vulnerability Report on huntr.dev (embargoed +30 days)","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.16"]},{"certainty":"source_listed","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (4.9)\n\n### Problem\nIt has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.\n\nExtension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new `MimicServiceInterface::mimicAuthUser`, which simulates corresponding times regular processing would usually take.\n\n### Solution\nUpdate to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.\n\n### Credits\nThanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2022-007\n* Vulnerability Report on huntr.dev (embargoed +30 days)","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.32"]},{"certainty":"source_listed","source_ids":["sr-f1ced0489e02b6b1185b548289d0f9e9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (4.9)\n\n### Problem\nIt has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.\n\nExtension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new `MimicServiceInterface::mimicAuthUser`, which simulates corresponding times regular processing would usually take.\n\n### Solution\nUpdate to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.\n\n### Credits\nThanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2022-007\n* Vulnerability Report on huntr.dev (embargoed +30 days)","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.16"]}],"null_published_at":"2026-10-31T22:13:22.825Z","source_updated_at":"2023-12-06T01:02:29.779Z","source_disclosed_at":"2022-09-16T17:16:28.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:30.972Z"}],"next_cursor":null,"snapshot_revision":"42594"}