Description
Winter CMS is a content management system built on the Laravel PHP framework. In versions up to and including 1.2.12, the CMS section's Theme Editor AJAX handlers did not enforce per-template-type permission checks, allowing a backend user with any single CMS permission to act on template types outside their authorized scope. The CMS controller gated access to the section as a whole using OR-logic across its five permissions, but individual handlers such as onSave(), onDelete(), and onDeleteTemplates() did not verify that the user held the specific permission for the requested template type, so a user with only cms.manage_pages could craft AJAX requests to delete layouts, modify partials, or read content files. Separately, the AssetList widget was registered for any user who passed the controller gate regardless of the cms.manage_assets permission, and its onUpload() handler omitted the theme-validation call present on the other mutating handlers, permitting unauthorized file uploads into the active theme's asset directory. Exploitation requires an authenticated backend account holding at least one of the CMS Theme Editor permissions. This issue is fixed in version 1.2.13.
Published: 2026-08-26
Score: 6.8 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The flaw in Winter CMS involves missing per‑template permission checks in the Theme Editor AJAX handlers – an authenticated backend user with any CMS permission that the system knows about can trigger actions such as deleting layouts, modifying partials, or reading content files for template types outside the user’s authorized scope. The vulnerability also allows the AssetList widget to upload files to the active theme’s asset directory because the usual theme‑validation guard is omitted. These weaknesses give an attacker with minimal CMS privileges the ability to alter website structure, inject malicious assets, and compromise site integrity.

Affected Systems

Winter CMS, versions up to and including 1.2.12. The fix is implemented in Winter CMS v1.2.13. All installations of the content management system built on the Laravel PHP framework that use those versions are affected.

Risk and Exploitability

The CVSS score of 6.8 indicates moderate severity. EPSS data is not available, and the vulnerability is not listed in the CISA KEV catalog, indicating no public exploits are known. Exploitation requires an authenticated backend account that holds at least one CMS Theme Editor permission, so it is limited to environments where such credentials exist. Once compromised, the attacker can perform dangerous content manipulation or upload malicious files.

Generated by OpenCVE AI on August 26, 2026 at 20:12 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Winter CMS to version 1.2.13 or later to apply the developed patch.
  • Limit backend user accounts to the minimum necessary CMS permissions, ensuring users only have the specific theme or asset rights required.
  • Implement monitoring to detect unauthorized file uploads in the theme asset directories and audit template changes regularly.

Generated by OpenCVE AI on August 26, 2026 at 20:12 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-5c4f-9pq9-6c77 Winter: Broken access control in `Cms\Controllers\Index` allows cross-template actions and unauthorized asset uploads
History

Wed, 26 Aug 2026 20:15:00 +0000

Type Values Removed Values Added
First Time appeared Wintercms
Wintercms winter
Vendors & Products Wintercms
Wintercms winter

Wed, 26 Aug 2026 18:00:00 +0000

Type Values Removed Values Added
Description Winter CMS is a content management system built on the Laravel PHP framework. In versions up to and including 1.2.12, the CMS section's Theme Editor AJAX handlers did not enforce per-template-type permission checks, allowing a backend user with any single CMS permission to act on template types outside their authorized scope. The CMS controller gated access to the section as a whole using OR-logic across its five permissions, but individual handlers such as onSave(), onDelete(), and onDeleteTemplates() did not verify that the user held the specific permission for the requested template type, so a user with only cms.manage_pages could craft AJAX requests to delete layouts, modify partials, or read content files. Separately, the AssetList widget was registered for any user who passed the controller gate regardless of the cms.manage_assets permission, and its onUpload() handler omitted the theme-validation call present on the other mutating handlers, permitting unauthorized file uploads into the active theme's asset directory. Exploitation requires an authenticated backend account holding at least one of the CMS Theme Editor permissions. This issue is fixed in version 1.2.13.
Title Winter: Broken access control in `Cms\Controllers\Index` allows cross-template actions and unauthorized asset uploads
Weaknesses CWE-289
References
Metrics cvssV3_1

{'score': 6.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N'}


Subscriptions

Wintercms Winter
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-26T17:50:32.102Z

Reserved: 2026-03-12T15:29:36.560Z

Link: CVE-2026-32639

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-26T18:16:30.427

Modified: 2026-08-26T18:16:30.427

Link: CVE-2026-32639

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-26T20:15:03Z

Weaknesses
  • CWE-289

    Authentication Bypass by Alternate Name