{"items":[{"id":"NVI-00004643","kind":"vulnerability","title":"Cleartext storage of session identifier","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-qx3w-4864-94ch","CVE-2021-21339"],"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 6.2.57 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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 7.6.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.40 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.14 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.1.1 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.25 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.14 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.1.1 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.25 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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-78083217cbdfaef06010738bfdc22595"],"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-17T03:35:19.860Z","value":"5 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-a7afc90958d7cb6fd199347bc0b3763c"},{"kind":"CVSS","as_of":"2026-06-17T03:35:19.860Z","value":"5.9 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-a7afc90958d7cb6fd199347bc0b3763c"},{"kind":"CVSS","as_of":"2026-06-17T03:35:19.860Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-a7afc90958d7cb6fd199347bc0b3763c"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.918%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.60234. Missing scores are unknown.","source_id":"sr-78083217cbdfaef06010738bfdc22595"}],"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-6e1f7293841b5f8d3258f7b7a6052fea","url":"https://github.com/advisories/GHSA-qx3w-4864-94ch","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-qx3w-4864-94ch","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.354Z"},{"id":"sr-a7afc90958d7cb6fd199347bc0b3763c","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-21339","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2021-21339","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T22:07:35.928Z"},{"id":"sr-78083217cbdfaef06010738bfdc22595","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-2021-21339","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 6.2.0; fixed 6.2.57"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.6.51"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.40"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]}],"null_published_at":"2026-11-01T19:14:01.607Z","source_updated_at":"2026-07-08T06:29:14.883Z","source_disclosed_at":"2021-03-23T01:53:42.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:41.354Z"},{"id":"NVI-00004643","kind":"vulnerability","title":"Cleartext storage of session identifier","revision":2,"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-qx3w-4864-94ch","CVE-2021-21339"],"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 6.2.57 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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 7.6.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.40 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.14 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.1.1 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.25 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.14 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.1.1 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.25 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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-a7afc90958d7cb6fd199347bc0b3763c"],"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-17T03:35:19.860Z","value":"5 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-a7afc90958d7cb6fd199347bc0b3763c"},{"kind":"CVSS","as_of":"2026-06-17T03:35:19.860Z","value":"5.9 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-a7afc90958d7cb6fd199347bc0b3763c"},{"kind":"CVSS","as_of":"2026-06-17T03:35:19.860Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-a7afc90958d7cb6fd199347bc0b3763c"}],"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-6e1f7293841b5f8d3258f7b7a6052fea","url":"https://github.com/advisories/GHSA-qx3w-4864-94ch","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-qx3w-4864-94ch","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.354Z"},{"id":"sr-a7afc90958d7cb6fd199347bc0b3763c","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-21339","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2021-21339","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T22:07:35.928Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 6.2.0; fixed 6.2.57"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.6.51"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.40"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]}],"null_published_at":"2026-10-31T22:27:12.395Z","source_updated_at":"2026-07-08T06:29:14.883Z","source_disclosed_at":"2021-03-23T01:53:42.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:41.354Z"},{"id":"NVI-00004643","kind":"vulnerability","title":"Cleartext storage of session identifier","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-qx3w-4864-94ch","CVE-2021-21339"],"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 6.2.57 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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 7.6.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.40 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.14 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.1.1 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.25 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.14 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.1.1 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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.25 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"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-6e1f7293841b5f8d3258f7b7a6052fea","url":"https://github.com/advisories/GHSA-qx3w-4864-94ch","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-qx3w-4864-94ch","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.354Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 6.2.0; fixed 6.2.57"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.6.51"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.40"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-6e1f7293841b5f8d3258f7b7a6052fea"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nUser session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.\n\n### Solution\nUpdate to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-006","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]}],"null_published_at":"2026-10-31T22:12:57.136Z","source_updated_at":"2026-07-08T06:29:14.883Z","source_disclosed_at":"2021-03-23T01:53:42.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:41.354Z"}],"next_cursor":null,"snapshot_revision":"42594"}