Winter CMS: CSRF through AJAX handler names reachable as backend page actions
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| wintercms | winter | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Wintercms | Winter |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-p2ch-c2c3-4xm5 | Winter: CSRF through AJAX handler names reachable as backend page actions |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.175% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wintercms
Wintercms winter |
|
| Vendors & Products |
Wintercms
Wintercms winter |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Winter CMS: CSRF through AJAX handler names reachable as backend page actions | |
| Weaknesses | CWE-352 | |
| References |
| |
| Metrics |
cvssV3_1
|