CVE-2026-32639: Winter Broken Access Control Vulnerability

MODERATE
Advisory Identifier: GHSA-5c4f-9pq9-6c77
CVSS 6.8
CWE-280
Published
Advisory Summary

CVE-2026-32639 is a MODERATE (CVSS 6.8) broken access control vulnerability (CWE-280: Improper Handling of Insufficient Permissions or Privileges) affecting Winter libraries in the Packagist ecosystem. The issue involves broken access control in `cms\controllers\index` allows cross-template actions and unauthorized asset uploads. Remediation is available by upgrading affected packages to version 1.2.13.

CVE-2026-32639 at a Glance

CVE Identifier CVE-2026-32639
GHSA Identifier GHSA-5c4f-9pq9-6c77
Severity MODERATE
CVSS v3.1 Base Score 6.8
CWE Classification CWE-280: Improper Handling of Insufficient Permissions or Privileges
Affected Product Winter
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 6.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-32639

To remediate this vulnerability, upgrade all affected Winter dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

winter/wn-cms-module fixed: 1.2.13
Upgrade winter/wn-cms-module to 1.2.13
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for winter/wn-cms-module

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-32639, inspect your project dependencies for Winter:

inspect dependencies for winter/wn-cms-module

Analyze the terminal output to locate any version of Winter in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.2.13), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-280: Improper Handling of Insufficient Permissions or Privileges, where the product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. this may cause it to follow unexpected code paths that may leave the product in an invalid state. In Winter, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Affected versions of Winter CMS did not enforce per-template-type permission checks in the CMS section's AJAX handlers. The CMS controller (`Cms\Controllers\Index`) used OR-logic across its five permissions (`cms.manage_pages`, `cms.manage_partials`, `cms.manage_layouts`, `cms.manage_content`, `cms.manage_assets`) to control access to the section as a whole, but individual handlers such as `onSave()`, `onDelete()`, and `onDeleteTemplates()` did not verify that the authenticated user holds the specific permission corresponding to the requested template type. This allowed a backend user with any single Theme Editor permission (e.g. `cms.manage_pages`) to craft AJAX requests targeting template types outside their authorized scope — for example, deleting layouts, modifying partials, or reading content files. In addition, the `AssetList` widget was registered for all users who passed the controller gate regardless of whether they held the `cms.manage_assets` permission, and its `onUpload()` handler was missing the `validateRequestTheme()` call that is present on all other mutating handlers in the same widget. This allowed unauthorized file uploads into the active theme's asset directory. To actively exploit this security issue, an attacker would need access to the Backend with a user account with any of the following permissions: - `cms.manage_pages` - `cms.manage_partials` - `cms.manage_layouts` - `cms.manage_content` - `cms.manage_assets` The Winter CMS maintainers strongly recommend that all Winter CMS sites that rely on granular CMS permission assignments (specifically users with only access to `cms.manage_content` to only be able to edit content files through the Theme Editor) to update immediately. ### Patches Per-template-type permission checks are now enforced on all Theme Editor AJAX handlers, the `AssetList` widget is only registered for users with the `cms.manage_assets` permission, and `onUpload()` now includes theme validation consistent with the other mutating handlers. This security issue has been fixed as of v1.2.13. ### Workarounds If users cannot upgrade, they may apply the following changes to their Winter CMS installation manually to resolve this issue: 1. In `modules/cms/controllers/Index.php`, wrap each widget registration in the constructor with the corresponding `hasAccess()` check, and add a `validateRequestType()` call to the `index_onOpenTemplate()`, `onSave()`, `onCreateTemplate()`, `onDeleteTemplates()`, `onDelete()`, `onCommit()`, and `onReset()` handlers that verifies the user holds the permission for the requested template type. 2. In `modules/cms/widgets/AssetList.php`, add a `$this->validateRequestTheme()` call at the top of the `onUpload()` method.

CVE-2026-32639 Affected Winter Versions

1 component(s)
Fixed Versions:
1.2.13
Product / Package Ecosystem Affected Versions Fixed Version
winter/wn-cms-module
Packagist
< 1.2.13
1.2.13

References

Frequently Asked Questions

What is CVE-2026-32639?
CVE-2026-32639 is a security vulnerability in Winter involving Broken access control in `Cms\Controllers\Index` allows cross-template actions and unauthorized asset uploads under CWE-280: Improper Handling of Insufficient Permissions or Privileges.
Which Winter versions are affected?
Affected versions include releases prior to 1.2.13 across affected packages: winter/wn-cms-module.
What version fixes CVE-2026-32639?
Upgrading to 1.2.13 (or the latest patched release for your respective branch) resolves the vulnerability.
Is winter/wn-cms-module affected?
Yes, winter/wn-cms-module is affected in releases prior to 1.2.13. Upgrade your dependency to 1.2.13 or later.
What is the CVSS score of CVE-2026-32639?
CVE-2026-32639 has a CVSS v3.1 base score of 6.8 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N.
What CWE is associated with CVE-2026-32639?
CVE-2026-32639 is classified under CWE-280: Improper Handling of Insufficient Permissions or Privileges (The product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the product in an invalid state.).
How can I check Packagist dependencies for CVE-2026-32639?
Run the dependency tree command: 'inspect dependencies for winter/wn-cms-module'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5c4f-9pq9-6c77",
  "modified" : "2026-08-12T15:14:47Z",
  "published" : "2026-08-12T15:14:47Z",
  "aliases" : [ "CVE-2026-32639" ],
  "summary" : "Winter: Broken access control in `Cms\\Controllers\\Index` allows cross-template actions and unauthorized asset uploads",
  "details" : "### Impact\n\nAffected versions of Winter CMS did not enforce per-template-type permission checks in the CMS section's AJAX handlers. The CMS controller (`Cms\\Controllers\\Index`) used OR-logic across its five permissions (`cms.manage_pages`, `cms.manage_partials`, `cms.manage_layouts`, `cms.manage_content`, `cms.manage_assets`) to control access to the section as a whole, but individual handlers such as `onSave()`, `onDelete()`, and `onDeleteTemplates()` did not verify that the authenticated user holds the specific permission corresponding to the requested template type.\n\nThis allowed a backend user with any single Theme Editor permission (e.g. `cms.manage_pages`) to craft AJAX requests targeting template types outside their authorized scope — for example, deleting layouts, modifying partials, or reading content files.\n\nIn addition, the `AssetList` widget was registered for all users who passed the controller gate regardless of whether they held the `cms.manage_assets` permission, and its `onUpload()` handler was missing the `validateRequestTheme()` call that is present on all other mutating handlers in the same widget. This allowed unauthorized file uploads into the active theme's asset directory.\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\n- `cms.manage_pages`\n- `cms.manage_partials`\n- `cms.manage_layouts`\n- `cms.manage_content`\n- `cms.manage_assets`\n\nThe Winter CMS maintainers strongly recommend that all Winter CMS sites that rely on granular CMS permission assignments (specifically users with only access to `cms.manage_content` to only be able to edit content files through the Theme Editor) to update immediately.\n\n### Patches\n\nPer-template-type permission checks are now enforced on all Theme Editor AJAX handlers, the `AssetList` widget is only registered for users with the `cms.manage_assets` permission, and `onUpload()` now includes theme validation consistent with the other mutating handlers.\n\nThis security issue has been fixed as of v1.2.13.\n\n### Workarounds\n\nIf users cannot upgrade, they may apply the following changes to their Winter CMS installation manually to resolve this issue:\n\n1. In `modules/cms/controllers/Index.php`, wrap each widget registration in the constructor with the corresponding `hasAccess()` check, and add a `validateRequestType()` call to the `index_onOpenTemplate()`, `onSave()`, `onCreateTemplate()`, `onDeleteTemplates()`, `onDelete()`, `onCommit()`, and `onReset()` handlers that verifies the user holds the permission for the requested template type.\n2. In `modules/cms/widgets/AssetList.php`, add a `$this->validateRequestTheme()` call at the top of the `onUpload()` method.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "winter/wn-cms-module"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.2.13"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.2.12"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/wintercms/winter/security/advisories/GHSA-5c4f-9pq9-6c77"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/wintercms/winter"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/wintercms/winter/releases/tag/v1.2.13"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-280" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-12T15:14:47Z",
    "nvd_published_at" : null
  }
}