CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



GHSA-P2CH-C2C3-4XM5

GHSA-P2CH-C2C3-4XM5: Cross-Site Request Forgery in Winter CMS AJAX Routing

Amit Schendel
Amit Schendel
Senior Security Researcher

Aug 21, 2026·4 min read·13 visits

Executive Summary (TL;DR)

An administrative routing bypass in Winter CMS allows attackers to execute highly privileged AJAX handlers via standard HTTP GET requests through cross-site request forgery, leading to unauthorized state-changing operations.

Winter CMS contains a routing bypass vulnerability that allows Cross-Site Request Forgery (CSRF) attacks to trigger administrative AJAX handlers. Due to case-insensitivity in PHP's method resolution and an insufficiently strict check in the backend controller system, an attacker can invoke these handler methods through lowercase HTTP GET requests, bypassing default CSRF token validation.

Vulnerability Overview

Winter CMS is an open-source, extensible content management system built on the Laravel framework.

The backend panel features an AJAX framework that facilitates asynchronous administrative actions. These actions are handled by specific controller methods, commonly referred to as AJAX handlers, which process administrative request payloads.

A routing mechanism flaw allows authenticated administrative AJAX handlers to be executed through standard HTTP GET requests. This route bypass exposes the application to cross-site request forgery attacks because the GET routing path bypasses the default CSRF protection middleware.

Because administrative users maintain broad permissions over layouts, database operations, and logs, the impact of unauthorized execution remains high.

Root Cause Analysis

The underlying vulnerability is located within the request-to-action routing engine of the Winter CMS backend controller class.

In PHP, method names are case-insensitive. When an administrator requests a path like /backend/system/eventlogs/index_onemptylog, the routing system verifies if the action exists in the controller using the actionExists verification method.

Because of PHP's case-insensitive method resolution, the lowercase URL string index_onemptylog successfully matches the mixed-case index_onEmptyLog method defined in the controller class.

Once matched, the framework dispatches the handler as a standard page action. Since standard HTTP GET requests do not trigger CSRF validation, the application processes the request and executes the administrative logic.

Code Analysis

The vulnerability is resolved by modifying the verification mechanism in the base controller class to strictly enforce matching casing for URL segments.

The original code relied on PHP's default reflection check, which implicitly ignores case differences. The following patch was introduced to compare the declared case of the method with the requested action name:

// In modules/backend/classes/Controller.php
if ($ownMethod) {
    $methodInfo = new \ReflectionMethod($this, $name);
 
    /*
     * Only allow lowercase actions. Compare the resolved method name rather than the
     * requested one - PHP method names are case-insensitive, so a lowercased URL
     * segment would otherwise pass this check and still resolve to the mixed-case
     * method (eg. "index_onemptylog" reaching index_onEmptyLog()).
     */
    if (strtolower($methodInfo->getName()) !== $methodInfo->getName()) {
        return false;
    }
 
    $public = $methodInfo->isPublic();
    if ($public) {
        return true;
    }
}

Additionally, the framework modified the parser function in BackendController.php to prevent camel-case conversion of dashed URL parameters during normalization:

// In modules/backend/classes/BackendController.php
protected function parseAction($actionName)
{
    if (strpos($actionName, '-') !== false) {
        return snake_case(camel_case($actionName));
    }
 
    return $actionName;
}

Exploitation

An attack requires an active administrator session and user interaction with a malicious link or embedded asset.

To perform the attack, an adversary constructs a URL targeting a sensitive AJAX handler, such as index_onEmptyLog inside the EventLogs controller, using its lowercased equivalent: index_onemptylog.

The adversary embeds this target URL within a malicious page or document. When the logged-in administrator visits the page, the browser automatically executes an authenticated GET request.

Because the request uses the GET method, CSRF defense mechanisms are not invoked. The application routes the call to the targeted handler, executing administrative functions without consent.

Impact Assessment

Successful exploitation allows cross-site request forgery attacks to execute arbitrary, highly privileged operations.

Attackers can achieve unauthorized data modifications such as deleting content management templates, truncating crucial logs, or disabling critical system settings.

The unofficial CVSS version 3.1 score is evaluated at 8.8 (High). This reflects the high impact on integrity and availability, combined with the requirement for user interaction.

Remediation and Detection

Administrators must upgrade Winter CMS installations to version 1.2.14 or later immediately.

To update the dependency via composer, execute composer update wintercms/winter.

Detection of exploitation attempts can be achieved by monitoring web access logs for GET requests containing strings such as index_on or other common handler suffixes.

A Web Application Firewall (WAF) rule can be configured to block GET requests matching known AJAX handler signatures on the backend paths.

Technical Appendix

CVSS Score
8.8/ 10

Affected Systems

Winter CMS installations running versions prior to v1.2.14
AttributeDetail
CWE IDCWE-352, CWE-178, CWE-862
Attack VectorNetwork (Remote)
CVSS v3.1 Score8.8
Exploit Statuspoc
KEV Statusnone

More Reports

•31 minutes ago•CVE-2026-103026
8.1

CVE-2026-103026: Arbitrary Method Invocation and State Tampering in Paymenter via Livewire HasConfirmation Trait

Paymenter versions prior to 1.5.7 contain an arbitrary method invocation vulnerability within the base Livewire component architecture. The application includes a legacy trait, HasConfirmation, inside app/Livewire/Component.php, which is inherited across 36 client-facing Livewire components. This trait exposes a public remote procedure call (RPC) endpoint named executeConfirmedAction without access controls or method allowlisting. Remote attackers can invoke arbitrary methods on any inheriting component, including Livewire's internal fill() method, enabling them to bypass #[Locked] property protections and manipulate internal component state and hydrated Eloquent models.

Alon Barad
Alon Barad
1 views•9 min read
•about 2 hours ago•CVE-2026-104885
6.3

CVE-2026-104885: Cross-Realm MQTT Session Disconnect via Missing Authorization in OpenRemote

OpenRemote prior to version 1.31.0 contains a Missing Authorization vulnerability (CWE-862) in the user management REST API endpoint responsible for disconnecting active MQTT sessions. The disconnectUserSession method in UserResourceImpl fails to verify whether the requesting user owns the target MQTT session, holds administrative privileges, or belongs to the realm specified in the request path. As a result, any authenticated user who obtains a valid MQTT session identifier can forcefully terminate active MQTT connections belonging to other users or IoT devices across any tenant realm.

Amit Schendel
Amit Schendel
2 views•9 min read
•about 3 hours ago•CVE-2026-69133
5.3

CVE-2026-69133: Cumulation Buffer Memory Retention in Netty OHTTP Codec

CVE-2026-69133 (GHSA-cg26-4c6j-2x8h) is a missing resource release vulnerability (CWE-772) in io.netty.incubator:netty-incubator-codec-ohttp affecting versions 0.0.20.Final through 0.0.26.Final. Both OHttpClientCodec and OHttpServerCodec retain the outer cumulationBuffer at its expanded high-water capacity after an Oblivious HTTP (OHTTP) exchange finishes. A remote unauthenticated attacker can complete a large OHTTP request or response over an HTTP keep-alive connection and leave the connection idle, pinning pooled or direct memory allocations across concurrent connections to induce denial of service.

Amit Schendel
Amit Schendel
2 views•8 min read
•about 3 hours ago•CVE-2026-104773
6.8

CVE-2026-104773: Session Fixation in CKAN User Registration View

A session fixation vulnerability (CWE-384) exists in CKAN (Comprehensive Knowledge Archive Network) prior to versions 2.10.11 and 2.11.6. When configured with server-side session storage and active public web registration, the user registration view programmatically authenticates newly created accounts without regenerating the active session identifier. An attacker capable of fixing or capturing a victim's pre-authentication session cookie can hijack the newly registered account immediately after registration completes.

Alon Barad
Alon Barad
2 views•9 min read
•about 4 hours ago•CVE-2026-35374
6.3

CVE-2026-35374: Arbitrary File Truncation via TOCTOU Race Condition in uutils coreutils split

CVE-2026-35374 is a Time-of-Check to Time-of-Use (TOCTOU) race condition (CWE-367) in the split utility of uutils coreutils. The utility validates that the input and output paths do not refer to the same file before opening the output file with truncation flags. A local attacker with write permissions in the destination directory can replace the output file path with a symbolic link during this race window, causing the process to truncate and overwrite arbitrary files accessible to the user executing split.

Amit Schendel
Amit Schendel
2 views•11 min read
•about 6 hours ago•CVE-2026-35377
3.3

CVE-2026-35377: Local Denial of Service via Improper Single-Quote Backslash Parsing in uutils coreutils env

CVE-2026-35377 is an improper input validation vulnerability (CWE-20) in the env utility of uutils coreutils, the Rust-based reimplementation of GNU coreutils. When processing command-line arguments with the -S (--split-string) option, the uutils split-string tokenizer erroneously validates backslash sequences enclosed within single quotes against a fixed table of known escape characters. Under standard GNU env behavior, backslashes inside single quotes are treated literally (except for \\ and \'). Because uutils rejects unrecognized sequences such as \a, \x, or \| with exit code 125, automated scripts, shebang invocations, and administrative workflows relying on POSIX/GNU compatibility fail to execute, resulting in a local denial of service.

Alon Barad
Alon Barad
2 views•9 min read