{"items":[{"id":"NVI-00003861","kind":"vulnerability","title":"Winter vulnerable to privilege escalation by authenticated backend users","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-pgpf-m8m4-6cg6","CVE-2026-27591"],"plain_summary":"OSV carries this publisher advisory for winter/wn-backend-module, winter/wn-backend-module, winter/wn-backend-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.12 for winter/wn-backend-module. Confirm the publisher’s latest guidance.","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"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.12 for winter/wn-backend-module. Confirm the publisher’s latest guidance.","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"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.477 for winter/wn-backend-module. Confirm the publisher’s latest guidance.","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"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-2c8f5521aa3f5cd55802c7ca0d628b6d"],"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-17T10:27:21.463Z","value":"9.9 CRITICAL (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-7d4813facf6eea9d6dc1cd65eec3b860"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.688%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.5271. Missing scores are unknown.","source_id":"sr-2c8f5521aa3f5cd55802c7ca0d628b6d"}],"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-4da0ac17c980aaa9f3c087206824272a","url":"https://github.com/advisories/GHSA-pgpf-m8m4-6cg6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-pgpf-m8m4-6cg6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.990Z"},{"id":"sr-7d4813facf6eea9d6dc1cd65eec3b860","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-27591","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-27591","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T01:40:56.268Z"},{"id":"sr-2c8f5521aa3f5cd55802c7ca0d628b6d","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-27591","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.849Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"technology":"winter/wn-backend-module","known_exclusions":[],"conditions_summary":"## Impact\nAffected versions of Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.\n\nThe Winter CMS maintainers strongly recommend that all Winter CMS sites that have any reliance on the roles & permissions system to update immediately. Security fixes have been backported to all major versions of Winter (1.0, 1.1, and 1.2).\n\n## Patches\nMultiple fixes and defence in depth has been applied to prevent current and future privilege escalation attacks at the lowest level possible.\n\nThis security issue has been fixed as of https://wintercms.com/releases/v1.0.477, https://wintercms.com/releases/v1.1.12, https://wintercms.com/releases/v1.2.12.\n\n## Workarounds\nIf you cannot upgrade, you may apply the changes from the releases to your Winter CMS installation manually to resolve this issue.","public_affected_ranges":["ECOSYSTEM: introduced 1.2.0; fixed 1.2.12"]},{"certainty":"source_listed","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"technology":"winter/wn-backend-module","known_exclusions":[],"conditions_summary":"## Impact\nAffected versions of Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.\n\nThe Winter CMS maintainers strongly recommend that all Winter CMS sites that have any reliance on the roles & permissions system to update immediately. Security fixes have been backported to all major versions of Winter (1.0, 1.1, and 1.2).\n\n## Patches\nMultiple fixes and defence in depth has been applied to prevent current and future privilege escalation attacks at the lowest level possible.\n\nThis security issue has been fixed as of https://wintercms.com/releases/v1.0.477, https://wintercms.com/releases/v1.1.12, https://wintercms.com/releases/v1.2.12.\n\n## Workarounds\nIf you cannot upgrade, you may apply the changes from the releases to your Winter CMS installation manually to resolve this issue.","public_affected_ranges":["ECOSYSTEM: introduced 1.1.0; fixed 1.1.12"]},{"certainty":"source_listed","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"technology":"winter/wn-backend-module","known_exclusions":[],"conditions_summary":"## Impact\nAffected versions of Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.\n\nThe Winter CMS maintainers strongly recommend that all Winter CMS sites that have any reliance on the roles & permissions system to update immediately. Security fixes have been backported to all major versions of Winter (1.0, 1.1, and 1.2).\n\n## Patches\nMultiple fixes and defence in depth has been applied to prevent current and future privilege escalation attacks at the lowest level possible.\n\nThis security issue has been fixed as of https://wintercms.com/releases/v1.0.477, https://wintercms.com/releases/v1.1.12, https://wintercms.com/releases/v1.2.12.\n\n## Workarounds\nIf you cannot upgrade, you may apply the changes from the releases to your Winter CMS installation manually to resolve this issue.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.0.477"]}],"null_published_at":"2026-11-08T19:53:38.916Z","source_updated_at":"2026-03-14T02:26:20.728Z","source_disclosed_at":"2026-03-12T14:07:39.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:30.990Z"},{"id":"NVI-00003861","kind":"vulnerability","title":"Winter vulnerable to privilege escalation by authenticated backend users","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-pgpf-m8m4-6cg6","CVE-2026-27591"],"plain_summary":"OSV carries this publisher advisory for winter/wn-backend-module, winter/wn-backend-module, winter/wn-backend-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.12 for winter/wn-backend-module. Confirm the publisher’s latest guidance.","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"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.12 for winter/wn-backend-module. Confirm the publisher’s latest guidance.","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"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.477 for winter/wn-backend-module. Confirm the publisher’s latest guidance.","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"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-827566b65ba0d36370254a52a8b62232"],"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-17T10:27:21.463Z","value":"9.9 CRITICAL (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-7d4813facf6eea9d6dc1cd65eec3b860"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.688%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.52728. Missing scores are unknown.","source_id":"sr-827566b65ba0d36370254a52a8b62232"}],"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-4da0ac17c980aaa9f3c087206824272a","url":"https://github.com/advisories/GHSA-pgpf-m8m4-6cg6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-pgpf-m8m4-6cg6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.990Z"},{"id":"sr-7d4813facf6eea9d6dc1cd65eec3b860","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-27591","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-27591","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T01:40:56.268Z"},{"id":"sr-827566b65ba0d36370254a52a8b62232","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-27591","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.376Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"technology":"winter/wn-backend-module","known_exclusions":[],"conditions_summary":"## Impact\nAffected versions of Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.\n\nThe Winter CMS maintainers strongly recommend that all Winter CMS sites that have any reliance on the roles & permissions system to update immediately. Security fixes have been backported to all major versions of Winter (1.0, 1.1, and 1.2).\n\n## Patches\nMultiple fixes and defence in depth has been applied to prevent current and future privilege escalation attacks at the lowest level possible.\n\nThis security issue has been fixed as of https://wintercms.com/releases/v1.0.477, https://wintercms.com/releases/v1.1.12, https://wintercms.com/releases/v1.2.12.\n\n## Workarounds\nIf you cannot upgrade, you may apply the changes from the releases to your Winter CMS installation manually to resolve this issue.","public_affected_ranges":["ECOSYSTEM: introduced 1.2.0; fixed 1.2.12"]},{"certainty":"source_listed","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"technology":"winter/wn-backend-module","known_exclusions":[],"conditions_summary":"## Impact\nAffected versions of Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.\n\nThe Winter CMS maintainers strongly recommend that all Winter CMS sites that have any reliance on the roles & permissions system to update immediately. Security fixes have been backported to all major versions of Winter (1.0, 1.1, and 1.2).\n\n## Patches\nMultiple fixes and defence in depth has been applied to prevent current and future privilege escalation attacks at the lowest level possible.\n\nThis security issue has been fixed as of https://wintercms.com/releases/v1.0.477, https://wintercms.com/releases/v1.1.12, https://wintercms.com/releases/v1.2.12.\n\n## Workarounds\nIf you cannot upgrade, you may apply the changes from the releases to your Winter CMS installation manually to resolve this issue.","public_affected_ranges":["ECOSYSTEM: introduced 1.1.0; fixed 1.1.12"]},{"certainty":"source_listed","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"technology":"winter/wn-backend-module","known_exclusions":[],"conditions_summary":"## Impact\nAffected versions of Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.\n\nThe Winter CMS maintainers strongly recommend that all Winter CMS sites that have any reliance on the roles & permissions system to update immediately. Security fixes have been backported to all major versions of Winter (1.0, 1.1, and 1.2).\n\n## Patches\nMultiple fixes and defence in depth has been applied to prevent current and future privilege escalation attacks at the lowest level possible.\n\nThis security issue has been fixed as of https://wintercms.com/releases/v1.0.477, https://wintercms.com/releases/v1.1.12, https://wintercms.com/releases/v1.2.12.\n\n## Workarounds\nIf you cannot upgrade, you may apply the changes from the releases to your Winter CMS installation manually to resolve this issue.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.0.477"]}],"null_published_at":"2026-11-03T17:49:21.346Z","source_updated_at":"2026-03-14T02:26:20.728Z","source_disclosed_at":"2026-03-12T14:07:39.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:30.990Z"},{"id":"NVI-00003861","kind":"vulnerability","title":"Winter vulnerable to privilege escalation by authenticated backend users","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pgpf-m8m4-6cg6","CVE-2026-27591"],"plain_summary":"OSV carries this publisher advisory for winter/wn-backend-module, winter/wn-backend-module, winter/wn-backend-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.12 for winter/wn-backend-module. Confirm the publisher’s latest guidance.","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"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.12 for winter/wn-backend-module. Confirm the publisher’s latest guidance.","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"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.477 for winter/wn-backend-module. Confirm the publisher’s latest guidance.","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"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-827566b65ba0d36370254a52a8b62232"],"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.688%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.52728. Missing scores are unknown.","source_id":"sr-827566b65ba0d36370254a52a8b62232"}],"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-4da0ac17c980aaa9f3c087206824272a","url":"https://github.com/advisories/GHSA-pgpf-m8m4-6cg6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-pgpf-m8m4-6cg6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.990Z"},{"id":"sr-827566b65ba0d36370254a52a8b62232","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-27591","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.376Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"technology":"winter/wn-backend-module","known_exclusions":[],"conditions_summary":"## Impact\nAffected versions of Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.\n\nThe Winter CMS maintainers strongly recommend that all Winter CMS sites that have any reliance on the roles & permissions system to update immediately. Security fixes have been backported to all major versions of Winter (1.0, 1.1, and 1.2).\n\n## Patches\nMultiple fixes and defence in depth has been applied to prevent current and future privilege escalation attacks at the lowest level possible.\n\nThis security issue has been fixed as of https://wintercms.com/releases/v1.0.477, https://wintercms.com/releases/v1.1.12, https://wintercms.com/releases/v1.2.12.\n\n## Workarounds\nIf you cannot upgrade, you may apply the changes from the releases to your Winter CMS installation manually to resolve this issue.","public_affected_ranges":["ECOSYSTEM: introduced 1.2.0; fixed 1.2.12"]},{"certainty":"source_listed","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"technology":"winter/wn-backend-module","known_exclusions":[],"conditions_summary":"## Impact\nAffected versions of Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.\n\nThe Winter CMS maintainers strongly recommend that all Winter CMS sites that have any reliance on the roles & permissions system to update immediately. Security fixes have been backported to all major versions of Winter (1.0, 1.1, and 1.2).\n\n## Patches\nMultiple fixes and defence in depth has been applied to prevent current and future privilege escalation attacks at the lowest level possible.\n\nThis security issue has been fixed as of https://wintercms.com/releases/v1.0.477, https://wintercms.com/releases/v1.1.12, https://wintercms.com/releases/v1.2.12.\n\n## Workarounds\nIf you cannot upgrade, you may apply the changes from the releases to your Winter CMS installation manually to resolve this issue.","public_affected_ranges":["ECOSYSTEM: introduced 1.1.0; fixed 1.1.12"]},{"certainty":"source_listed","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"technology":"winter/wn-backend-module","known_exclusions":[],"conditions_summary":"## Impact\nAffected versions of Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.\n\nThe Winter CMS maintainers strongly recommend that all Winter CMS sites that have any reliance on the roles & permissions system to update immediately. Security fixes have been backported to all major versions of Winter (1.0, 1.1, and 1.2).\n\n## Patches\nMultiple fixes and defence in depth has been applied to prevent current and future privilege escalation attacks at the lowest level possible.\n\nThis security issue has been fixed as of https://wintercms.com/releases/v1.0.477, https://wintercms.com/releases/v1.1.12, https://wintercms.com/releases/v1.2.12.\n\n## Workarounds\nIf you cannot upgrade, you may apply the changes from the releases to your Winter CMS installation manually to resolve this issue.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.0.477"]}],"null_published_at":"2026-11-03T02:33:09.089Z","source_updated_at":"2026-03-14T02:26:20.728Z","source_disclosed_at":"2026-03-12T14:07:39.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:30.990Z"},{"id":"NVI-00003861","kind":"vulnerability","title":"Winter vulnerable to privilege escalation by authenticated backend users","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pgpf-m8m4-6cg6","CVE-2026-27591"],"plain_summary":"OSV carries this publisher advisory for winter/wn-backend-module, winter/wn-backend-module, winter/wn-backend-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.12 for winter/wn-backend-module. Confirm the publisher’s latest guidance.","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"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.12 for winter/wn-backend-module. Confirm the publisher’s latest guidance.","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"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.477 for winter/wn-backend-module. Confirm the publisher’s latest guidance.","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"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-4da0ac17c980aaa9f3c087206824272a","url":"https://github.com/advisories/GHSA-pgpf-m8m4-6cg6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-pgpf-m8m4-6cg6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.990Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"technology":"winter/wn-backend-module","known_exclusions":[],"conditions_summary":"## Impact\nAffected versions of Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.\n\nThe Winter CMS maintainers strongly recommend that all Winter CMS sites that have any reliance on the roles & permissions system to update immediately. Security fixes have been backported to all major versions of Winter (1.0, 1.1, and 1.2).\n\n## Patches\nMultiple fixes and defence in depth has been applied to prevent current and future privilege escalation attacks at the lowest level possible.\n\nThis security issue has been fixed as of https://wintercms.com/releases/v1.0.477, https://wintercms.com/releases/v1.1.12, https://wintercms.com/releases/v1.2.12.\n\n## Workarounds\nIf you cannot upgrade, you may apply the changes from the releases to your Winter CMS installation manually to resolve this issue.","public_affected_ranges":["ECOSYSTEM: introduced 1.2.0; fixed 1.2.12"]},{"certainty":"source_listed","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"technology":"winter/wn-backend-module","known_exclusions":[],"conditions_summary":"## Impact\nAffected versions of Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.\n\nThe Winter CMS maintainers strongly recommend that all Winter CMS sites that have any reliance on the roles & permissions system to update immediately. Security fixes have been backported to all major versions of Winter (1.0, 1.1, and 1.2).\n\n## Patches\nMultiple fixes and defence in depth has been applied to prevent current and future privilege escalation attacks at the lowest level possible.\n\nThis security issue has been fixed as of https://wintercms.com/releases/v1.0.477, https://wintercms.com/releases/v1.1.12, https://wintercms.com/releases/v1.2.12.\n\n## Workarounds\nIf you cannot upgrade, you may apply the changes from the releases to your Winter CMS installation manually to resolve this issue.","public_affected_ranges":["ECOSYSTEM: introduced 1.1.0; fixed 1.1.12"]},{"certainty":"source_listed","source_ids":["sr-4da0ac17c980aaa9f3c087206824272a"],"technology":"winter/wn-backend-module","known_exclusions":[],"conditions_summary":"## Impact\nAffected versions of Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.\n\nThe Winter CMS maintainers strongly recommend that all Winter CMS sites that have any reliance on the roles & permissions system to update immediately. Security fixes have been backported to all major versions of Winter (1.0, 1.1, and 1.2).\n\n## Patches\nMultiple fixes and defence in depth has been applied to prevent current and future privilege escalation attacks at the lowest level possible.\n\nThis security issue has been fixed as of https://wintercms.com/releases/v1.0.477, https://wintercms.com/releases/v1.1.12, https://wintercms.com/releases/v1.2.12.\n\n## Workarounds\nIf you cannot upgrade, you may apply the changes from the releases to your Winter CMS installation manually to resolve this issue.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.0.477"]}],"null_published_at":"2026-10-31T22:12:52.600Z","source_updated_at":"2026-03-14T02:26:20.728Z","source_disclosed_at":"2026-03-12T14:07:39.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:30.990Z"}],"next_cursor":null,"snapshot_revision":"42594"}