CVE-2026-32639 wintercms CVE debrief

Who should care

Defenders responsible for Winter CMS deployments should assess exposure and apply the patch to prevent unauthorized actions by authenticated backend users. This includes reviewing and restricting permissions for backend users to ensure they can only perform authorized actions. Additionally, defenders should verify exposure and apply the patch to prevent potential unauthorized actions. Operators, platform administrators, vulnerability management teams, and

Why it matters

CVE-2026-32639 is a vulnerability in Winter CMS that allows an authenticated backend user to perform unauthorized actions on template types outside their authorized scope. Defenders should prioritize verifying exposure and applying the patch.

• An authenticated backend user could perform unauthorized actions on template types outside their authorized scope.
• The vulnerability could lead to unauthorized modifications or deletions of templates, partials, or content files.
• Defenders should verify exposure and apply the patch to prevent potential unauthorized actions.

Technical summary

The vulnerability exists in the Theme Editor AJAX handlers of Winter CMS, which did not enforce per-template-type permission checks. This allows an authenticated backend user with any single CMS permission to perform unauthorized actions on template types outside their authorized scope. The issue is fixed in version 1.2.13. The vulnerability has a CVSS score of 6.8 and is considered MEDIUM severity. Defenders should prioritize verifying exposure and applying the patch to prevent potential unauthorized actions by authenticated backend users.

Defensive priority

Defenders should prioritize verifying exposure and applying the patch, as unauthorized actions could be performed by authenticated backend users.

Recommended defensive actions

• Verify exposure by checking if the Winter CMS version is 1.2.12 or earlier.
• Apply the patch by upgrading to Winter CMS version 1.2.13 or later.
• Review and restrict permissions for backend users to ensure they can only perform authorized actions.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. The vulnerability exists in Winter CMS versions up to and including 1.2.12. Defenders should verify exposure and apply the patch to prevent potential unauthorized actions by authenticated backend users. Evidence is limited to public CVE and NVD records, so further verification is required to confirm affected scope and severity.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.