{"items":[{"id":"NVI-00004999","kind":"vulnerability","title":"Winter CMS Modules allows a sandbox bypass in Twig templates leading to data modification and deletion","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-xhw3-4j3m-hq53","CVE-2024-54149"],"plain_summary":"OSV carries this publisher advisory for winter/wn-cms-module, winter/wn-cms-module, winter/wn-cms-module. 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 1.2.7 for winter/wn-cms-module. Confirm the publisher’s latest guidance.","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"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 1.1.11 for winter/wn-cms-module. Confirm the publisher’s latest guidance.","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"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 1.0.476 for winter/wn-cms-module. Confirm the publisher’s latest guidance.","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"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-803454dd0ce949fff40f9604412d1139"],"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-17T08:09:51.670Z","value":"8.4 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-cab1bc4ece7a1fa3da1098b7994db200"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.420%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.3639. Missing scores are unknown.","source_id":"sr-803454dd0ce949fff40f9604412d1139"}],"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-7ca1f5d815a4b532ea5de1e07387983b","url":"https://github.com/advisories/GHSA-xhw3-4j3m-hq53","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-xhw3-4j3m-hq53","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:51.445Z"},{"id":"sr-cab1bc4ece7a1fa3da1098b7994db200","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-54149","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2024-54149","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:59:51.327Z"},{"id":"sr-803454dd0ce949fff40f9604412d1139","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-2024-54149","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.369Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"technology":"winter/wn-cms-module","known_exclusions":[],"conditions_summary":"### Impact\n\nAffected versions of Winter CMS allow users with access to the CMS templates sections that modify Twig files to bypass the sandbox placed on Twig files and modify resources such as theme customisation values or modify, or remove, templates in the theme even if not provided direct access via the permissions.\n\nAs all objects passed through to Twig are references to the live objects, it is also possible to also manipulate model data if models are passed directly to Twig, including changing attributes or even removing records entirely. In most cases, this is unwanted behavior and potentially dangerous.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any of the following permissions:\n- `cms.manage_layouts`\n- `cms.manage_pages`\n- `cms.manage_partials`\n\nThe Winter CMS maintainers strongly recommend that these permissions only be reserved to trusted administrators and developers in general.\n\n### Patches\n\nIn order to mitigate this issue, we have significantly increased the scope of the sandbox, effectively making all models and datasources read-only in Twig.\n\nThis security issue has been fixed as of https://github.c","public_affected_ranges":["ECOSYSTEM: introduced 1.2.0; fixed 1.2.7"]},{"certainty":"source_listed","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"technology":"winter/wn-cms-module","known_exclusions":[],"conditions_summary":"### Impact\n\nAffected versions of Winter CMS allow users with access to the CMS templates sections that modify Twig files to bypass the sandbox placed on Twig files and modify resources such as theme customisation values or modify, or remove, templates in the theme even if not provided direct access via the permissions.\n\nAs all objects passed through to Twig are references to the live objects, it is also possible to also manipulate model data if models are passed directly to Twig, including changing attributes or even removing records entirely. In most cases, this is unwanted behavior and potentially dangerous.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any of the following permissions:\n- `cms.manage_layouts`\n- `cms.manage_pages`\n- `cms.manage_partials`\n\nThe Winter CMS maintainers strongly recommend that these permissions only be reserved to trusted administrators and developers in general.\n\n### Patches\n\nIn order to mitigate this issue, we have significantly increased the scope of the sandbox, effectively making all models and datasources read-only in Twig.\n\nThis security issue has been fixed as of https://github.c","public_affected_ranges":["ECOSYSTEM: introduced 1.1.0; fixed 1.1.11"]},{"certainty":"source_listed","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"technology":"winter/wn-cms-module","known_exclusions":[],"conditions_summary":"### Impact\n\nAffected versions of Winter CMS allow users with access to the CMS templates sections that modify Twig files to bypass the sandbox placed on Twig files and modify resources such as theme customisation values or modify, or remove, templates in the theme even if not provided direct access via the permissions.\n\nAs all objects passed through to Twig are references to the live objects, it is also possible to also manipulate model data if models are passed directly to Twig, including changing attributes or even removing records entirely. In most cases, this is unwanted behavior and potentially dangerous.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any of the following permissions:\n- `cms.manage_layouts`\n- `cms.manage_pages`\n- `cms.manage_partials`\n\nThe Winter CMS maintainers strongly recommend that these permissions only be reserved to trusted administrators and developers in general.\n\n### Patches\n\nIn order to mitigate this issue, we have significantly increased the scope of the sandbox, effectively making all models and datasources read-only in Twig.\n\nThis security issue has been fixed as of https://github.c","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.0.476"]}],"null_published_at":"2026-11-07T22:29:23.428Z","source_updated_at":"2026-09-10T03:50:21.801Z","source_disclosed_at":"2024-12-09T20:41:41.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:51.445Z"},{"id":"NVI-00004999","kind":"vulnerability","title":"Winter CMS Modules allows a sandbox bypass in Twig templates leading to data modification and deletion","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-xhw3-4j3m-hq53","CVE-2024-54149"],"plain_summary":"OSV carries this publisher advisory for winter/wn-cms-module, winter/wn-cms-module, winter/wn-cms-module. 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 1.2.7 for winter/wn-cms-module. Confirm the publisher’s latest guidance.","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"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 1.1.11 for winter/wn-cms-module. Confirm the publisher’s latest guidance.","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"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 1.0.476 for winter/wn-cms-module. Confirm the publisher’s latest guidance.","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"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-803454dd0ce949fff40f9604412d1139"],"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.420%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.3639. Missing scores are unknown.","source_id":"sr-803454dd0ce949fff40f9604412d1139"}],"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-7ca1f5d815a4b532ea5de1e07387983b","url":"https://github.com/advisories/GHSA-xhw3-4j3m-hq53","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-xhw3-4j3m-hq53","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:51.445Z"},{"id":"sr-803454dd0ce949fff40f9604412d1139","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-2024-54149","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.369Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"technology":"winter/wn-cms-module","known_exclusions":[],"conditions_summary":"### Impact\n\nAffected versions of Winter CMS allow users with access to the CMS templates sections that modify Twig files to bypass the sandbox placed on Twig files and modify resources such as theme customisation values or modify, or remove, templates in the theme even if not provided direct access via the permissions.\n\nAs all objects passed through to Twig are references to the live objects, it is also possible to also manipulate model data if models are passed directly to Twig, including changing attributes or even removing records entirely. In most cases, this is unwanted behavior and potentially dangerous.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any of the following permissions:\n- `cms.manage_layouts`\n- `cms.manage_pages`\n- `cms.manage_partials`\n\nThe Winter CMS maintainers strongly recommend that these permissions only be reserved to trusted administrators and developers in general.\n\n### Patches\n\nIn order to mitigate this issue, we have significantly increased the scope of the sandbox, effectively making all models and datasources read-only in Twig.\n\nThis security issue has been fixed as of https://github.c","public_affected_ranges":["ECOSYSTEM: introduced 1.2.0; fixed 1.2.7"]},{"certainty":"source_listed","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"technology":"winter/wn-cms-module","known_exclusions":[],"conditions_summary":"### Impact\n\nAffected versions of Winter CMS allow users with access to the CMS templates sections that modify Twig files to bypass the sandbox placed on Twig files and modify resources such as theme customisation values or modify, or remove, templates in the theme even if not provided direct access via the permissions.\n\nAs all objects passed through to Twig are references to the live objects, it is also possible to also manipulate model data if models are passed directly to Twig, including changing attributes or even removing records entirely. In most cases, this is unwanted behavior and potentially dangerous.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any of the following permissions:\n- `cms.manage_layouts`\n- `cms.manage_pages`\n- `cms.manage_partials`\n\nThe Winter CMS maintainers strongly recommend that these permissions only be reserved to trusted administrators and developers in general.\n\n### Patches\n\nIn order to mitigate this issue, we have significantly increased the scope of the sandbox, effectively making all models and datasources read-only in Twig.\n\nThis security issue has been fixed as of https://github.c","public_affected_ranges":["ECOSYSTEM: introduced 1.1.0; fixed 1.1.11"]},{"certainty":"source_listed","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"technology":"winter/wn-cms-module","known_exclusions":[],"conditions_summary":"### Impact\n\nAffected versions of Winter CMS allow users with access to the CMS templates sections that modify Twig files to bypass the sandbox placed on Twig files and modify resources such as theme customisation values or modify, or remove, templates in the theme even if not provided direct access via the permissions.\n\nAs all objects passed through to Twig are references to the live objects, it is also possible to also manipulate model data if models are passed directly to Twig, including changing attributes or even removing records entirely. In most cases, this is unwanted behavior and potentially dangerous.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any of the following permissions:\n- `cms.manage_layouts`\n- `cms.manage_pages`\n- `cms.manage_partials`\n\nThe Winter CMS maintainers strongly recommend that these permissions only be reserved to trusted administrators and developers in general.\n\n### Patches\n\nIn order to mitigate this issue, we have significantly increased the scope of the sandbox, effectively making all models and datasources read-only in Twig.\n\nThis security issue has been fixed as of https://github.c","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.0.476"]}],"null_published_at":"2026-11-03T02:33:09.079Z","source_updated_at":"2026-09-10T03:50:21.801Z","source_disclosed_at":"2024-12-09T20:41:41.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:51.445Z"},{"id":"NVI-00004999","kind":"vulnerability","title":"Winter CMS Modules allows a sandbox bypass in Twig templates leading to data modification and deletion","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-xhw3-4j3m-hq53","CVE-2024-54149"],"plain_summary":"OSV carries this publisher advisory for winter/wn-cms-module, winter/wn-cms-module, winter/wn-cms-module. 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 1.2.7 for winter/wn-cms-module. Confirm the publisher’s latest guidance.","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"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 1.1.11 for winter/wn-cms-module. Confirm the publisher’s latest guidance.","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"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 1.0.476 for winter/wn-cms-module. Confirm the publisher’s latest guidance.","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"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-7ca1f5d815a4b532ea5de1e07387983b","url":"https://github.com/advisories/GHSA-xhw3-4j3m-hq53","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-xhw3-4j3m-hq53","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:51.445Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"technology":"winter/wn-cms-module","known_exclusions":[],"conditions_summary":"### Impact\n\nAffected versions of Winter CMS allow users with access to the CMS templates sections that modify Twig files to bypass the sandbox placed on Twig files and modify resources such as theme customisation values or modify, or remove, templates in the theme even if not provided direct access via the permissions.\n\nAs all objects passed through to Twig are references to the live objects, it is also possible to also manipulate model data if models are passed directly to Twig, including changing attributes or even removing records entirely. In most cases, this is unwanted behavior and potentially dangerous.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any of the following permissions:\n- `cms.manage_layouts`\n- `cms.manage_pages`\n- `cms.manage_partials`\n\nThe Winter CMS maintainers strongly recommend that these permissions only be reserved to trusted administrators and developers in general.\n\n### Patches\n\nIn order to mitigate this issue, we have significantly increased the scope of the sandbox, effectively making all models and datasources read-only in Twig.\n\nThis security issue has been fixed as of https://github.c","public_affected_ranges":["ECOSYSTEM: introduced 1.2.0; fixed 1.2.7"]},{"certainty":"source_listed","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"technology":"winter/wn-cms-module","known_exclusions":[],"conditions_summary":"### Impact\n\nAffected versions of Winter CMS allow users with access to the CMS templates sections that modify Twig files to bypass the sandbox placed on Twig files and modify resources such as theme customisation values or modify, or remove, templates in the theme even if not provided direct access via the permissions.\n\nAs all objects passed through to Twig are references to the live objects, it is also possible to also manipulate model data if models are passed directly to Twig, including changing attributes or even removing records entirely. In most cases, this is unwanted behavior and potentially dangerous.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any of the following permissions:\n- `cms.manage_layouts`\n- `cms.manage_pages`\n- `cms.manage_partials`\n\nThe Winter CMS maintainers strongly recommend that these permissions only be reserved to trusted administrators and developers in general.\n\n### Patches\n\nIn order to mitigate this issue, we have significantly increased the scope of the sandbox, effectively making all models and datasources read-only in Twig.\n\nThis security issue has been fixed as of https://github.c","public_affected_ranges":["ECOSYSTEM: introduced 1.1.0; fixed 1.1.11"]},{"certainty":"source_listed","source_ids":["sr-7ca1f5d815a4b532ea5de1e07387983b"],"technology":"winter/wn-cms-module","known_exclusions":[],"conditions_summary":"### Impact\n\nAffected versions of Winter CMS allow users with access to the CMS templates sections that modify Twig files to bypass the sandbox placed on Twig files and modify resources such as theme customisation values or modify, or remove, templates in the theme even if not provided direct access via the permissions.\n\nAs all objects passed through to Twig are references to the live objects, it is also possible to also manipulate model data if models are passed directly to Twig, including changing attributes or even removing records entirely. In most cases, this is unwanted behavior and potentially dangerous.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any of the following permissions:\n- `cms.manage_layouts`\n- `cms.manage_pages`\n- `cms.manage_partials`\n\nThe Winter CMS maintainers strongly recommend that these permissions only be reserved to trusted administrators and developers in general.\n\n### Patches\n\nIn order to mitigate this issue, we have significantly increased the scope of the sandbox, effectively making all models and datasources read-only in Twig.\n\nThis security issue has been fixed as of https://github.c","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.0.476"]}],"null_published_at":"2026-10-31T22:12:57.150Z","source_updated_at":"2026-09-10T03:50:21.801Z","source_disclosed_at":"2024-12-09T20:41:41.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:51.445Z"}],"next_cursor":null,"snapshot_revision":"42594"}