Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.8amended

Winter: Broken access control in Cms\Controllers\Index allows cross-template actions and unauthorized asset uploads

CVE-2026-32639GHSA-5c4f-9pq9-6c77

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (winter/wn-cms-module 1.2.13), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.8 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
EPSS
  • CVE-2026-32639: 0.46% estimated exploitation activity in the next 30 days; percentile 39.85 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.managepages, cms.managepartials, cms.managelayouts, cms.managecontent, cms.manageassets) 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.managepages) 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.manageassets permission, and its onUpload() handler was missing the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-5c4f-9pq9-6c77

  2. Revision 1 · created ·

    Published from osv record GHSA-5c4f-9pq9-6c77

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32639

Advisory: Winter: Broken access control in `Cms\Controllers\Index` allows cross-template actions and unauthorized asset uploads
IDs: CVE-2026-32639, GHSA-5c4f-9pq9-6c77
Record: https://patchnext.com/advisories/cve-2026-32639 (revision 2, source checked 26 Oct 2026, 14:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: winter/wn-cms-module 1.2.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist winter/wn-cms-module: affected <= 1.2.12; fixed in 1.2.13

## Suggested inspection (read-only)
- Packagist winter/wn-cms-module: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on winter/wn-cms-module.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-5c4f-9pq9-6c77 (OSV record GHSA-5c4f-9pq9-6c77 lists affected ranges: Packagist winter/wn-cms-module >=0 <1.2.13 (fixed))
- Verified: https://github.com/advisories/GHSA-5c4f-9pq9-6c77 (GitHub-reviewed advisory GHSA-5c4f-9pq9-6c77 lists affected ranges: Packagist winter/wn-cms-module >=0 <=1.2.12)

Commands are suggestions: review each one before running it.

Loading voting…