{"items":[{"id":"NVI-00003431","kind":"vulnerability","title":"Exposure of Sensitive Information to an Unauthorized Actor in TYPO3 CMS","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-3x94-fv5h-5q2c","CVE-2020-15099"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms, typo3/cms. 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 9.5.20 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"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.6 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"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.6 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"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.20 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"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-8d6783b0266bf0d3b60eba05960a459a"],"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-17T02:56:03.123Z","value":"6.8 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-21b651e53d9716fbb4f9803d638a3ef3"},{"kind":"CVSS","as_of":"2026-06-17T02:56:03.123Z","value":"8.1 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-21b651e53d9716fbb4f9803d638a3ef3"},{"kind":"CVSS","as_of":"2026-06-17T02:56:03.123Z","value":"8.1 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-21b651e53d9716fbb4f9803d638a3ef3"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"1.790%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.78365. Missing scores are unknown.","source_id":"sr-8d6783b0266bf0d3b60eba05960a459a"}],"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-3e21cac9c893e9a6d055edeb5ff29de1","url":"https://github.com/advisories/GHSA-3x94-fv5h-5q2c","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-3x94-fv5h-5q2c","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.661Z"},{"id":"sr-21b651e53d9716fbb4f9803d638a3ef3","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-15099","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2020-15099","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T22:07:06.394Z"},{"id":"sr-8d6783b0266bf0d3b60eba05960a459a","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-2020-15099","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5)\n> * CWE-20, CWE-200\n\n### Problem\nIn case an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case the internal _encryptionKey_ was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used.\n\nIn case a database server is directly accessible either via internet or in a shared hosting network, this allows to completely retrieve, manipulate or delete database contents. This includes creating an administration user account - which can be used to trigger remote code execution by injecting custom extensions.\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2020-007","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.20"]},{"certainty":"source_listed","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5)\n> * CWE-20, CWE-200\n\n### Problem\nIn case an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case the internal _encryptionKey_ was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used.\n\nIn case a database server is directly accessible either via internet or in a shared hosting network, this allows to completely retrieve, manipulate or delete database contents. This includes creating an administration user account - which can be used to trigger remote code execution by injecting custom extensions.\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2020-007","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.6"]},{"certainty":"source_listed","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5)\n> * CWE-20, CWE-200\n\n### Problem\nIn case an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case the internal _encryptionKey_ was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used.\n\nIn case a database server is directly accessible either via internet or in a shared hosting network, this allows to completely retrieve, manipulate or delete database contents. This includes creating an administration user account - which can be used to trigger remote code execution by injecting custom extensions.\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2020-007","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.6"]},{"certainty":"source_listed","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5)\n> * CWE-20, CWE-200\n\n### Problem\nIn case an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case the internal _encryptionKey_ was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used.\n\nIn case a database server is directly accessible either via internet or in a shared hosting network, this allows to completely retrieve, manipulate or delete database contents. This includes creating an administration user account - which can be used to trigger remote code execution by injecting custom extensions.\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2020-007","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.20"]}],"null_published_at":"2026-11-03T02:33:09.139Z","source_updated_at":"2026-07-08T06:28:13.715Z","source_disclosed_at":"2020-07-29T16:15:32.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:41:49.661Z"},{"id":"NVI-00003431","kind":"vulnerability","title":"Exposure of Sensitive Information to an Unauthorized Actor in TYPO3 CMS","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-3x94-fv5h-5q2c","CVE-2020-15099"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms, typo3/cms. 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 9.5.20 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"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.6 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"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.6 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"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.20 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"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-21b651e53d9716fbb4f9803d638a3ef3"],"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-17T02:56:03.123Z","value":"6.8 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-21b651e53d9716fbb4f9803d638a3ef3"},{"kind":"CVSS","as_of":"2026-06-17T02:56:03.123Z","value":"8.1 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-21b651e53d9716fbb4f9803d638a3ef3"},{"kind":"CVSS","as_of":"2026-06-17T02:56:03.123Z","value":"8.1 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-21b651e53d9716fbb4f9803d638a3ef3"}],"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-3e21cac9c893e9a6d055edeb5ff29de1","url":"https://github.com/advisories/GHSA-3x94-fv5h-5q2c","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-3x94-fv5h-5q2c","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.661Z"},{"id":"sr-21b651e53d9716fbb4f9803d638a3ef3","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-15099","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2020-15099","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T22:07:06.394Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5)\n> * CWE-20, CWE-200\n\n### Problem\nIn case an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case the internal _encryptionKey_ was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used.\n\nIn case a database server is directly accessible either via internet or in a shared hosting network, this allows to completely retrieve, manipulate or delete database contents. This includes creating an administration user account - which can be used to trigger remote code execution by injecting custom extensions.\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2020-007","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.20"]},{"certainty":"source_listed","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5)\n> * CWE-20, CWE-200\n\n### Problem\nIn case an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case the internal _encryptionKey_ was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used.\n\nIn case a database server is directly accessible either via internet or in a shared hosting network, this allows to completely retrieve, manipulate or delete database contents. This includes creating an administration user account - which can be used to trigger remote code execution by injecting custom extensions.\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2020-007","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.6"]},{"certainty":"source_listed","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5)\n> * CWE-20, CWE-200\n\n### Problem\nIn case an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case the internal _encryptionKey_ was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used.\n\nIn case a database server is directly accessible either via internet or in a shared hosting network, this allows to completely retrieve, manipulate or delete database contents. This includes creating an administration user account - which can be used to trigger remote code execution by injecting custom extensions.\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2020-007","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.6"]},{"certainty":"source_listed","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5)\n> * CWE-20, CWE-200\n\n### Problem\nIn case an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case the internal _encryptionKey_ was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used.\n\nIn case a database server is directly accessible either via internet or in a shared hosting network, this allows to completely retrieve, manipulate or delete database contents. This includes creating an administration user account - which can be used to trigger remote code execution by injecting custom extensions.\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2020-007","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.20"]}],"null_published_at":"2026-10-31T22:27:03.544Z","source_updated_at":"2026-07-08T06:28:13.715Z","source_disclosed_at":"2020-07-29T16:15:32.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:41:49.661Z"},{"id":"NVI-00003431","kind":"vulnerability","title":"Exposure of Sensitive Information to an Unauthorized Actor in TYPO3 CMS","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-3x94-fv5h-5q2c","CVE-2020-15099"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms, typo3/cms. 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 9.5.20 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"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.6 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"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.6 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"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.20 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"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-3e21cac9c893e9a6d055edeb5ff29de1","url":"https://github.com/advisories/GHSA-3x94-fv5h-5q2c","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-3x94-fv5h-5q2c","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.661Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5)\n> * CWE-20, CWE-200\n\n### Problem\nIn case an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case the internal _encryptionKey_ was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used.\n\nIn case a database server is directly accessible either via internet or in a shared hosting network, this allows to completely retrieve, manipulate or delete database contents. This includes creating an administration user account - which can be used to trigger remote code execution by injecting custom extensions.\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2020-007","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.20"]},{"certainty":"source_listed","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5)\n> * CWE-20, CWE-200\n\n### Problem\nIn case an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case the internal _encryptionKey_ was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used.\n\nIn case a database server is directly accessible either via internet or in a shared hosting network, this allows to completely retrieve, manipulate or delete database contents. This includes creating an administration user account - which can be used to trigger remote code execution by injecting custom extensions.\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2020-007","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.6"]},{"certainty":"source_listed","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5)\n> * CWE-20, CWE-200\n\n### Problem\nIn case an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case the internal _encryptionKey_ was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used.\n\nIn case a database server is directly accessible either via internet or in a shared hosting network, this allows to completely retrieve, manipulate or delete database contents. This includes creating an administration user account - which can be used to trigger remote code execution by injecting custom extensions.\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2020-007","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.6"]},{"certainty":"source_listed","source_ids":["sr-3e21cac9c893e9a6d055edeb5ff29de1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5)\n> * CWE-20, CWE-200\n\n### Problem\nIn case an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case the internal _encryptionKey_ was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used.\n\nIn case a database server is directly accessible either via internet or in a shared hosting network, this allows to completely retrieve, manipulate or delete database contents. This includes creating an administration user account - which can be used to trigger remote code execution by injecting custom extensions.\n\n### Solution\nUpdate to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.\n\n### Credits\nThanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2020-007","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.20"]}],"null_published_at":"2026-10-31T22:12:48.016Z","source_updated_at":"2026-07-08T06:28:13.715Z","source_disclosed_at":"2020-07-29T16:15:32.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:41:49.661Z"}],"next_cursor":null,"snapshot_revision":"42594"}