GHSA-p2ch-c2c3-4xm5: Winter CSRF Through AJAX Handler Names Vulnerability

MODERATE
CVSS 6.1
CWE-352
Published
Advisory Summary

GHSA-p2ch-c2c3-4xm5 is a MODERATE (CVSS 6.1) csrf through ajax handler names vulnerability (CWE-352: Cross-Site Request Forgery (CSRF)) affecting Winter libraries in the Packagist ecosystem. The issue involves csrf through ajax handler names reachable as backend page actions. Remediation is available by upgrading affected packages to version 1.2.14.

GHSA-p2ch-c2c3-4xm5 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-p2ch-c2c3-4xm5
Severity MODERATE
CVSS v3.1 Base Score 6.1
CWE Classification CWE-352: Cross-Site Request Forgery (CSRF)
Affected Product Winter
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 6.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability High (A:H)

How to Fix GHSA-p2ch-c2c3-4xm5

To remediate this vulnerability, upgrade all affected Winter dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

winter/wn-backend-module fixed: 1.2.14
Upgrade winter/wn-backend-module to 1.2.14
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for winter/wn-backend-module

How to Check if You Are Affected

To determine whether your application is affected by GHSA-p2ch-c2c3-4xm5, inspect your project dependencies for Winter:

inspect dependencies for winter/wn-backend-module

Analyze the terminal output to locate any version of Winter in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.2.14), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-352: Cross-Site Request Forgery (CSRF), where the web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. In Winter, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Affected versions of Winter CMS allow a backend AJAX handler to be invoked by a plain top-level `GET` navigation with no CSRF token. `Backend\Classes\Controller::actionExists()` accepted any public method on a controller as a page action, so handler-shaped names were never reserved from URL dispatch: an authenticated and authorized request to `/backend/system/eventlogs/index_onEmptyLog` reached the handler of the same name and truncated the system event log. Backend paths are routed through `Route::any`, and CSRF validation is skipped for `HEAD`, `GET` and `OPTIONS` requests. The default `SameSite=Lax` session cookie is sent on top-level cross-site navigation, so a link on an attacker-controlled page is sufficient — no form, no script and no token. Handler arguments are taken from URL path segments, so the attacker also chooses the target record. Affected handlers across the `backend`, `cms` and `system` modules cover log truncation, resetting settings to their defaults, altering backend user state, and deleting CMS templates. None of them disclose data to the attacker or write attacker-controlled content, so the impact is destructive and state-changing rather than confidential. To actively exploit this issue, an attacker would need no account of their own, but would need an authenticated backend user holding the relevant permission to follow an attacker-supplied link. The permissions guarding the affected handlers, `system.access_logs` included, are by default assigned only to the built-in Developer role. ### Patches Page-action dispatch is now restricted to all-lowercase method names, which reserves handler-shaped names (`onFoo`, `index_onFoo`) from being reached by URL. AJAX dispatch is unchanged: handlers continue to work over `POST` with the `X-WINTER-REQUEST-HANDLER` header exactly as before, and need no changes. >**IMPORTANT:** **This fix includes a breaking change to backend action routing.** A public controller method used as a page action must now be named in lowercase — `coming_soon()` rather than `comingSoon()` — and dashed URLs are normalised to `snake_case`, so `/coming-soon` now resolves to `coming_soon()` instead of `comingSoon()`. Plugins with a camelCase page action should rename the method and its view file to match; the published URL does not need to change. Core is unaffected, and a survey of the plugin ecosystem found the change affects only a small number of plugins. This security issue has been fixed in [v1.2.14](https://github.com/wintercms/winter/commit/353b23804dee2acf49fca996c72637040446824f). ### Workarounds If you cannot upgrade, apply https://github.com/wintercms/winter/commit/353b23804dee2acf49fca996c72637040446824f manually. As an interim mitigation, set `'same_site' => 'strict'` in `config/session.php`. A strict session cookie is not sent on cross-site top-level navigation, which prevents the victim's session accompanying an attacker's link. Review this against any single sign-on or inbound-link flows into your backend first, as it also affects legitimate cross-site entry. ### References Credit to Awwader ([@NRAwwad](https://github.com/NRAwwad)) for reporting the issue. ### For more information If you have any questions or comments about this advisory: - Email us at [hello@wintercms.com](mailto:hello@wintercms.com)

GHSA-p2ch-c2c3-4xm5 Affected Winter Versions

1 component(s)
Fixed Versions:
1.2.14
Product / Package Ecosystem Affected Versions Fixed Version
winter/wn-backend-module
Packagist
≥ 1.0.319
< 1.2.14
1.2.14

References

Frequently Asked Questions

What is GHSA-p2ch-c2c3-4xm5?
GHSA-p2ch-c2c3-4xm5 is a security vulnerability in Winter involving CSRF through AJAX handler names reachable as backend page actions under CWE-352: Cross-Site Request Forgery (CSRF).
Which Winter versions are affected?
Affected versions include releases prior to 1.2.14 across affected packages: winter/wn-backend-module.
What version fixes GHSA-p2ch-c2c3-4xm5?
Upgrading to 1.2.14 (or the latest patched release for your respective branch) resolves the vulnerability.
Is winter/wn-backend-module affected?
Yes, winter/wn-backend-module is affected in releases prior to 1.2.14. Upgrade your dependency to 1.2.14 or later.
What is the CVSS score of GHSA-p2ch-c2c3-4xm5?
GHSA-p2ch-c2c3-4xm5 has a CVSS v3.1 base score of 6.1 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:H.
What CWE is associated with GHSA-p2ch-c2c3-4xm5?
GHSA-p2ch-c2c3-4xm5 is classified under CWE-352: Cross-Site Request Forgery (CSRF) (The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.).
How can I check Packagist dependencies for GHSA-p2ch-c2c3-4xm5?
Run the dependency tree command: 'inspect dependencies for winter/wn-backend-module'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-p2ch-c2c3-4xm5",
  "modified" : "2026-08-20T18:44:59Z",
  "published" : "2026-08-20T18:44:59Z",
  "aliases" : [ ],
  "summary" : "Winter: CSRF through AJAX handler names reachable as backend page actions",
  "details" : "### Impact\n\nAffected versions of Winter CMS allow a backend AJAX handler to be invoked by a plain top-level `GET` navigation with no CSRF token. `Backend\\Classes\\Controller::actionExists()` accepted any public method on a controller as a page action, so handler-shaped names were never reserved from URL dispatch: an authenticated and authorized request to `/backend/system/eventlogs/index_onEmptyLog` reached the handler of the same name and truncated the system event log. Backend paths are routed through `Route::any`, and CSRF validation is skipped for `HEAD`, `GET` and `OPTIONS` requests.\n\nThe default `SameSite=Lax` session cookie is sent on top-level cross-site navigation, so a link on an attacker-controlled page is sufficient — no form, no script and no token. Handler arguments are taken from URL path segments, so the attacker also chooses the target record. Affected handlers across the `backend`, `cms` and `system` modules cover log truncation, resetting settings to their defaults, altering backend user state, and deleting CMS templates. None of them disclose data to the attacker or write attacker-controlled content, so the impact is destructive and state-changing rather than confidential.\n\nTo actively exploit this issue, an attacker would need no account of their own, but would need an authenticated backend user holding the relevant permission to follow an attacker-supplied link. The permissions guarding the affected handlers, `system.access_logs` included, are by default assigned only to the built-in Developer role.\n\n### Patches\n\nPage-action dispatch is now restricted to all-lowercase method names, which reserves handler-shaped names (`onFoo`, `index_onFoo`) from being reached by URL. AJAX dispatch is unchanged: handlers continue to work over `POST` with the `X-WINTER-REQUEST-HANDLER` header exactly as before, and need no changes.\n\n>**IMPORTANT:** **This fix includes a breaking change to backend action routing.** A public controller method used as a page action must now be named in lowercase — `coming_soon()` rather than `comingSoon()` — and dashed URLs are normalised to `snake_case`, so `/coming-soon` now resolves to `coming_soon()` instead of `comingSoon()`. Plugins with a camelCase page action should rename the method and its view file to match; the published URL does not need to change. Core is unaffected, and a survey of the plugin ecosystem found the change affects only a small number of plugins.\n\nThis security issue has been fixed in [v1.2.14](https://github.com/wintercms/winter/commit/353b23804dee2acf49fca996c72637040446824f).\n\n### Workarounds\n\nIf you cannot upgrade, apply https://github.com/wintercms/winter/commit/353b23804dee2acf49fca996c72637040446824f manually.\n\nAs an interim mitigation, set `'same_site' => 'strict'` in `config/session.php`. A strict session cookie is not sent on cross-site top-level navigation, which prevents the victim's session accompanying an attacker's link. Review this against any single sign-on or inbound-link flows into your backend first, as it also affects legitimate cross-site entry.\n\n### References\n\nCredit to Awwader ([@NRAwwad](https://github.com/NRAwwad)) for reporting the issue.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n- Email us at [hello@wintercms.com](mailto:hello@wintercms.com)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "winter/wn-backend-module"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.0.319"
      }, {
        "fixed" : "1.2.14"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/wintercms/winter/security/advisories/GHSA-p2ch-c2c3-4xm5"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/wintercms/winter/commit/353b23804dee2acf49fca996c72637040446824f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/wintercms/winter"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/wintercms/winter/releases/tag/v1.2.14"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-352" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-20T18:44:59Z",
    "nvd_published_at" : null
  }
}