CVE-2026-125339: wintercms winter · Cross-Site Request Forgery
Affects wintercms winterSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium : upgrade to 1.2.14 when convenient.
Data as of 10 Nov 2026, 20:21 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 6.1 |
|---|
- Patch
- Available – fixed in 1.2.14
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade wintercms winter to 1.2.14.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| wintercmswinter | Affected
| Fixed in
|
AI-suggested
Upgrade Winter CMS to version 1.2.14 or later, where this CSRF vulnerability is fixed. No other mitigation is indicated by the vendor advisory.
Description
Winter CMS versions from 1.0.319 up to but not including 1.2.14 contain a Cross-Site Request Forgery (CSRF) vulnerability in backend AJAX handlers. This flaw allows an attacker to trick an authorized backend user into performing state-changing actions via specially crafted GET requests without a CSRF token. The vulnerability affects backend, CMS, and system modules, enabling actions such as truncating logs, resetting settings, altering user state, or deleting CMS templates. The issue is resolved in version 1.2.14.