{"items":[{"id":"NVI-00004328","kind":"vulnerability","title":"Contao: Improper access control in the table access voter","revision":5,"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-5974-gfqc-wrcm","CVE-2026-107851"],"plain_summary":"GitHub lists this reviewed advisory for contao/core-bundle. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-23143572970ebd7a5f292be1662bda39"],"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},{"summary":"The original advisory lists fixed boundaries 5.7.12 for contao/core-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-62250edaa6e7e1ef1ae16385ffb04f3a"],"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":[{"kind":"CVSS","as_of":"2026-10-09T20:53:42.000Z","value":"4.3 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-6045370470d13b58fb2b62ae12d824ef"},{"kind":"CVSS","as_of":"2026-10-16T20:04:29.760Z","value":"4.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-3d1ae213b47fe106a11a50dea6402cdf"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.193%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.09064. Missing scores are unknown.","source_id":"sr-23143572970ebd7a5f292be1662bda39"}],"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-6045370470d13b58fb2b62ae12d824ef","url":"https://github.com/advisories/GHSA-5974-gfqc-wrcm","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-5974-gfqc-wrcm","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:14:22.124Z"},{"id":"sr-62250edaa6e7e1ef1ae16385ffb04f3a","url":"https://github.com/advisories/GHSA-5974-gfqc-wrcm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-5974-gfqc-wrcm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.680Z"},{"id":"sr-3d1ae213b47fe106a11a50dea6402cdf","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-107851","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-107851","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T01:40:38.141Z"},{"id":"sr-23143572970ebd7a5f292be1662bda39","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-2026-107851","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.774Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6045370470d13b58fb2b62ae12d824ef"],"technology":"contao/core-bundle","known_exclusions":[],"conditions_summary":"Due to a caching defect in the security voter that governs table-level access to Contao's Data Container (DCA) backend, a low-privileged, non-admin backend user can obtain unauthorized read, create, update, and delete access to database tables outside their assigned module permissions. This includes tables containing sensitive personal data, such as frontend member records and newsletter subscriber e-mail addresses.\n\n### Vulnerability Details\n\nIn plain terms: Contao's backend is organized into modules (e.g. \"News\", \"Members\"). Every backend user is assigned to a group, and that group decides which modules, and therefore which database tables, they are allowed to work with. Before Contao lets a user touch a table, it is supposed to check: \"does this user's group actually include this table?\"\n\nTo avoid doing that check over and over, Contao remembers the answer for the rest of the request. The problem is that it remembers the answer under the wrong label. Instead of remembering \"is this user allowed to access table X\", it only remembers \"is this user allowed to access something\", without recording which table the answer was actually about.\n \nSo if a request first checks a table the u","public_affected_ranges":[">= 5.7.0, < 5.7.12"]},{"certainty":"source_listed","source_ids":["sr-62250edaa6e7e1ef1ae16385ffb04f3a"],"technology":"contao/core-bundle","known_exclusions":[],"conditions_summary":"Due to a caching defect in the security voter that governs table-level access to Contao's Data Container (DCA) backend, a low-privileged, non-admin backend user can obtain unauthorized read, create, update, and delete access to database tables outside their assigned module permissions. This includes tables containing sensitive personal data, such as frontend member records and newsletter subscriber e-mail addresses.\n\n### Vulnerability Details\n\nIn plain terms: Contao's backend is organized into modules (e.g. \"News\", \"Members\"). Every backend user is assigned to a group, and that group decides which modules, and therefore which database tables, they are allowed to work with. Before Contao lets a user touch a table, it is supposed to check: \"does this user's group actually include this table?\"\n\nTo avoid doing that check over and over, Contao remembers the answer for the rest of the request. The problem is that it remembers the answer under the wrong label. Instead of remembering \"is this user allowed to access table X\", it only remembers \"is this user allowed to access something\", without recording which table the answer was actually about.\n \nSo if a request first checks a table the u","public_affected_ranges":["ECOSYSTEM: introduced 5.7.0; fixed 5.7.12"]}],"null_published_at":"2026-11-08T19:53:33.517Z","source_updated_at":"2026-10-09T20:53:42.000Z","source_disclosed_at":"2026-10-09T20: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:41:49.680Z"},{"id":"NVI-00004328","kind":"vulnerability","title":"Contao: Improper access control in the table access voter","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-5974-gfqc-wrcm","CVE-2026-107851"],"plain_summary":"GitHub lists this reviewed advisory for contao/core-bundle. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-4090acf47c5dd0023a8eb32edd64cf68"],"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},{"summary":"The original advisory lists fixed boundaries 5.7.12 for contao/core-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-62250edaa6e7e1ef1ae16385ffb04f3a"],"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":[{"kind":"CVSS","as_of":"2026-10-09T20:53:42.000Z","value":"4.3 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-6045370470d13b58fb2b62ae12d824ef"},{"kind":"CVSS","as_of":"2026-10-16T20:04:29.760Z","value":"4.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-3d1ae213b47fe106a11a50dea6402cdf"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.193%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.09028. Missing scores are unknown.","source_id":"sr-4090acf47c5dd0023a8eb32edd64cf68"}],"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-6045370470d13b58fb2b62ae12d824ef","url":"https://github.com/advisories/GHSA-5974-gfqc-wrcm","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-5974-gfqc-wrcm","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:14:22.124Z"},{"id":"sr-62250edaa6e7e1ef1ae16385ffb04f3a","url":"https://github.com/advisories/GHSA-5974-gfqc-wrcm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-5974-gfqc-wrcm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.680Z"},{"id":"sr-3d1ae213b47fe106a11a50dea6402cdf","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-107851","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-107851","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T01:40:38.141Z"},{"id":"sr-4090acf47c5dd0023a8eb32edd64cf68","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-2026-107851","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.373Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6045370470d13b58fb2b62ae12d824ef"],"technology":"contao/core-bundle","known_exclusions":[],"conditions_summary":"Due to a caching defect in the security voter that governs table-level access to Contao's Data Container (DCA) backend, a low-privileged, non-admin backend user can obtain unauthorized read, create, update, and delete access to database tables outside their assigned module permissions. This includes tables containing sensitive personal data, such as frontend member records and newsletter subscriber e-mail addresses.\n\n### Vulnerability Details\n\nIn plain terms: Contao's backend is organized into modules (e.g. \"News\", \"Members\"). Every backend user is assigned to a group, and that group decides which modules, and therefore which database tables, they are allowed to work with. Before Contao lets a user touch a table, it is supposed to check: \"does this user's group actually include this table?\"\n\nTo avoid doing that check over and over, Contao remembers the answer for the rest of the request. The problem is that it remembers the answer under the wrong label. Instead of remembering \"is this user allowed to access table X\", it only remembers \"is this user allowed to access something\", without recording which table the answer was actually about.\n \nSo if a request first checks a table the u","public_affected_ranges":[">= 5.7.0, < 5.7.12"]},{"certainty":"source_listed","source_ids":["sr-62250edaa6e7e1ef1ae16385ffb04f3a"],"technology":"contao/core-bundle","known_exclusions":[],"conditions_summary":"Due to a caching defect in the security voter that governs table-level access to Contao's Data Container (DCA) backend, a low-privileged, non-admin backend user can obtain unauthorized read, create, update, and delete access to database tables outside their assigned module permissions. This includes tables containing sensitive personal data, such as frontend member records and newsletter subscriber e-mail addresses.\n\n### Vulnerability Details\n\nIn plain terms: Contao's backend is organized into modules (e.g. \"News\", \"Members\"). Every backend user is assigned to a group, and that group decides which modules, and therefore which database tables, they are allowed to work with. Before Contao lets a user touch a table, it is supposed to check: \"does this user's group actually include this table?\"\n\nTo avoid doing that check over and over, Contao remembers the answer for the rest of the request. The problem is that it remembers the answer under the wrong label. Instead of remembering \"is this user allowed to access table X\", it only remembers \"is this user allowed to access something\", without recording which table the answer was actually about.\n \nSo if a request first checks a table the u","public_affected_ranges":["ECOSYSTEM: introduced 5.7.0; fixed 5.7.12"]}],"null_published_at":"2026-11-01T14:34:07.630Z","source_updated_at":"2026-10-09T20:53:42.000Z","source_disclosed_at":"2026-10-09T20: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:41:49.680Z"},{"id":"NVI-00004328","kind":"vulnerability","title":"Contao: Improper access control in the table access voter","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-5974-gfqc-wrcm","CVE-2026-107851"],"plain_summary":"GitHub lists this reviewed advisory for contao/core-bundle. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-4090acf47c5dd0023a8eb32edd64cf68"],"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},{"summary":"The original advisory lists fixed boundaries 5.7.12 for contao/core-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-62250edaa6e7e1ef1ae16385ffb04f3a"],"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":[{"kind":"CVSS","as_of":"2026-10-09T20:53:42.000Z","value":"4.3 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-6045370470d13b58fb2b62ae12d824ef"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.193%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.09028. Missing scores are unknown.","source_id":"sr-4090acf47c5dd0023a8eb32edd64cf68"}],"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-6045370470d13b58fb2b62ae12d824ef","url":"https://github.com/advisories/GHSA-5974-gfqc-wrcm","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-5974-gfqc-wrcm","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:14:22.124Z"},{"id":"sr-62250edaa6e7e1ef1ae16385ffb04f3a","url":"https://github.com/advisories/GHSA-5974-gfqc-wrcm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-5974-gfqc-wrcm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.680Z"},{"id":"sr-4090acf47c5dd0023a8eb32edd64cf68","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-2026-107851","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.373Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6045370470d13b58fb2b62ae12d824ef"],"technology":"contao/core-bundle","known_exclusions":[],"conditions_summary":"Due to a caching defect in the security voter that governs table-level access to Contao's Data Container (DCA) backend, a low-privileged, non-admin backend user can obtain unauthorized read, create, update, and delete access to database tables outside their assigned module permissions. This includes tables containing sensitive personal data, such as frontend member records and newsletter subscriber e-mail addresses.\n\n### Vulnerability Details\n\nIn plain terms: Contao's backend is organized into modules (e.g. \"News\", \"Members\"). Every backend user is assigned to a group, and that group decides which modules, and therefore which database tables, they are allowed to work with. Before Contao lets a user touch a table, it is supposed to check: \"does this user's group actually include this table?\"\n\nTo avoid doing that check over and over, Contao remembers the answer for the rest of the request. The problem is that it remembers the answer under the wrong label. Instead of remembering \"is this user allowed to access table X\", it only remembers \"is this user allowed to access something\", without recording which table the answer was actually about.\n \nSo if a request first checks a table the u","public_affected_ranges":[">= 5.7.0, < 5.7.12"]},{"certainty":"source_listed","source_ids":["sr-62250edaa6e7e1ef1ae16385ffb04f3a"],"technology":"contao/core-bundle","known_exclusions":[],"conditions_summary":"Due to a caching defect in the security voter that governs table-level access to Contao's Data Container (DCA) backend, a low-privileged, non-admin backend user can obtain unauthorized read, create, update, and delete access to database tables outside their assigned module permissions. This includes tables containing sensitive personal data, such as frontend member records and newsletter subscriber e-mail addresses.\n\n### Vulnerability Details\n\nIn plain terms: Contao's backend is organized into modules (e.g. \"News\", \"Members\"). Every backend user is assigned to a group, and that group decides which modules, and therefore which database tables, they are allowed to work with. Before Contao lets a user touch a table, it is supposed to check: \"does this user's group actually include this table?\"\n\nTo avoid doing that check over and over, Contao remembers the answer for the rest of the request. The problem is that it remembers the answer under the wrong label. Instead of remembering \"is this user allowed to access table X\", it only remembers \"is this user allowed to access something\", without recording which table the answer was actually about.\n \nSo if a request first checks a table the u","public_affected_ranges":["ECOSYSTEM: introduced 5.7.0; fixed 5.7.12"]}],"null_published_at":"2026-11-01T01:03:56.616Z","source_updated_at":"2026-10-09T20:53:42.000Z","source_disclosed_at":"2026-10-09T20: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:41:49.680Z"},{"id":"NVI-00004328","kind":"vulnerability","title":"Contao: Improper access control in the table access voter","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-5974-gfqc-wrcm","CVE-2026-107851"],"plain_summary":"OSV carries this publisher advisory for contao/core-bundle. 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 5.7.12 for contao/core-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-62250edaa6e7e1ef1ae16385ffb04f3a"],"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-4090acf47c5dd0023a8eb32edd64cf68"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.193%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.09028. Missing scores are unknown.","source_id":"sr-4090acf47c5dd0023a8eb32edd64cf68"}],"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-62250edaa6e7e1ef1ae16385ffb04f3a","url":"https://github.com/advisories/GHSA-5974-gfqc-wrcm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-5974-gfqc-wrcm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.680Z"},{"id":"sr-4090acf47c5dd0023a8eb32edd64cf68","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-2026-107851","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.373Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-62250edaa6e7e1ef1ae16385ffb04f3a"],"technology":"contao/core-bundle","known_exclusions":[],"conditions_summary":"Due to a caching defect in the security voter that governs table-level access to Contao's Data Container (DCA) backend, a low-privileged, non-admin backend user can obtain unauthorized read, create, update, and delete access to database tables outside their assigned module permissions. This includes tables containing sensitive personal data, such as frontend member records and newsletter subscriber e-mail addresses.\n\n### Vulnerability Details\n\nIn plain terms: Contao's backend is organized into modules (e.g. \"News\", \"Members\"). Every backend user is assigned to a group, and that group decides which modules, and therefore which database tables, they are allowed to work with. Before Contao lets a user touch a table, it is supposed to check: \"does this user's group actually include this table?\"\n\nTo avoid doing that check over and over, Contao remembers the answer for the rest of the request. The problem is that it remembers the answer under the wrong label. Instead of remembering \"is this user allowed to access table X\", it only remembers \"is this user allowed to access something\", without recording which table the answer was actually about.\n \nSo if a request first checks a table the u","public_affected_ranges":["ECOSYSTEM: introduced 5.7.0; fixed 5.7.12"]}],"null_published_at":"2026-10-31T23:18:17.206Z","source_updated_at":"2026-10-09T21:00:08.462Z","source_disclosed_at":"2026-10-09T20: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:41:49.680Z"},{"id":"NVI-00004328","kind":"vulnerability","title":"Contao: Improper access control in the table access voter","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-5974-gfqc-wrcm","CVE-2026-107851"],"plain_summary":"OSV carries this publisher advisory for contao/core-bundle. 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 5.7.12 for contao/core-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-62250edaa6e7e1ef1ae16385ffb04f3a"],"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-62250edaa6e7e1ef1ae16385ffb04f3a","url":"https://github.com/advisories/GHSA-5974-gfqc-wrcm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-5974-gfqc-wrcm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.680Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-62250edaa6e7e1ef1ae16385ffb04f3a"],"technology":"contao/core-bundle","known_exclusions":[],"conditions_summary":"Due to a caching defect in the security voter that governs table-level access to Contao's Data Container (DCA) backend, a low-privileged, non-admin backend user can obtain unauthorized read, create, update, and delete access to database tables outside their assigned module permissions. This includes tables containing sensitive personal data, such as frontend member records and newsletter subscriber e-mail addresses.\n\n### Vulnerability Details\n\nIn plain terms: Contao's backend is organized into modules (e.g. \"News\", \"Members\"). Every backend user is assigned to a group, and that group decides which modules, and therefore which database tables, they are allowed to work with. Before Contao lets a user touch a table, it is supposed to check: \"does this user's group actually include this table?\"\n\nTo avoid doing that check over and over, Contao remembers the answer for the rest of the request. The problem is that it remembers the answer under the wrong label. Instead of remembering \"is this user allowed to access table X\", it only remembers \"is this user allowed to access something\", without recording which table the answer was actually about.\n \nSo if a request first checks a table the u","public_affected_ranges":["ECOSYSTEM: introduced 5.7.0; fixed 5.7.12"]}],"null_published_at":"2026-10-31T22:12:52.642Z","source_updated_at":"2026-10-09T21:00:08.462Z","source_disclosed_at":"2026-10-09T20: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:41:49.680Z"}],"next_cursor":null,"snapshot_revision":"42594"}