Read the docs

Cross-site request forgery in Winter CMS backend page actions

Priority LOW 26CWE-352Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
Required
Attack complexity
Low
Impact type
Tampering
Confidentiality · integrity · availability
None · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-352.

Summary

Winter CMS from 1.0.319 before 1.2.14 is affected. The backend controller accepts public methods named like AJAX handlers as page actions, so a top-level GET request can run state-changing backend handlers without a CSRF token (CWE-352). An unauthenticated attacker can get an authorized backend user to follow a crafted link, which can truncate logs, reset settings, alter backend user state, or delete CMS templates.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

Description from the CNA

Winter CMS is a content management system built on the Laravel PHP framework. From 1.0.319 until 1.2.14, Backend\Classes\Controller::actionExists() accepts public handler-shaped methods as page actions, so a top-level GET request can invoke state-changing backend AJAX handlers without a CSRF token. Because backend routes use Route::any, CSRF validation skips GET, and the default SameSite=Lax session cookie is sent on cross-site navigation, an unauthenticated attacker can induce an authorized backend user to follow a link such as /backend/system/eventlogs/index_onEmptyLog. Affected handlers in the backend, CMS, and system modules can truncate logs, reset settings, alter backend user state, or delete CMS templates, while URL path segments can select a target record. This issue is fixed in version 1.2.14.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00175 7th percentileScored 2026-11-16
Fix Fixed winter (wintercms): 1.2.14

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
wintercmswinter1.0.319 to before 1.2.141.2.14Patch availableCNA
  • winter Vendorwintercms Affected 1.0.319 to before 1.2.14 Fixed in 1.2.14 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:wintercms:winter:*:*:*:*:*:*:*:*——wintercms
  • cpe:2.3:a:wintercms:winter:*:*:*:*:*:*:*:* Versions — — ·wintercms

Remediation

Update Winter CMS to version 1.2.14, which fixes this flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

  • Fix · CNA winter (wintercms) Fixed in 1.2.14

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-125339
  2. 2026-11-12 Priority changed: MEDIUM → LOW
  3. 2026-11-12 CISA SSVC decision points changed

References

  • TI-2024-19497 Server-side Template Injection (SSTI) vulnerability in Winter CMS v.1.2.3 allows a remote… CVSS 3.1HIGH 7.2
  • TI-2023-28528 Winter CMS Local File Inclusion through Server Side Template Injection CVSS 3.1MEDIUM 5.4
  • TI-2022-18732 Winter vulnerable to Prototype Pollution in Snowboard framework CVSS 3.1CRITICAL 9.8
  • TI-2026-55251 Winter CMS before 1.2.13 Twig Sandbox Escape via SecurityPolicy CVSS 4.0CRITICAL 9.3
  • TI-2026-21979 Winter: Privilege escalation by authenticated backend users CVSS 3.1CRITICAL 10.0
  • TI-2024-21102 Dusk plugin may allow unfettered user authentication in misconfigured installs CVSS 3.1HIGH 8.8
See all 24 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences