Description

A weakness has been identified in light0011 cms c774dce31c6df0055568a8d5c53d964d99be199d/f72cf46f601efb2a0618c3814cc2f61380b38930. This affects an unknown part of the file App/Home/Model/UserModel.class.php of the component Cookie Helper. Executing a manipulation of the argument Username can lead to improper authentication. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The project was informed of the problem early through an issue report but has not responded yet.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.3",
  "pubDate": "2026-09-07T13:20:39.927Z",
  "pubdate": "2026-09-07T13:20:39.927Z",
  "executiveSummary": "A critical authentication vulnerability has been identified in light0011 cms, specifically within the Cookie Helper component.\nThe vulnerability manifests as an improper authentication flaw that can be exploited by manipulating the 'Username' argument.\nSuccessful exploitation allows a remote, unauthenticated attacker to bypass authentication mechanisms, potentially leading to unauthorized access to user accounts or administrative functions.\nThe vulnerability exists within the 'App/Home/Model/UserModel.class.php' file.\nGiven that public exploit code is already available, the risk to instances of this CMS is considered high.\nThe project utilizes a rolling release model, complicating patch management as specific version numbers are not explicitly defined or disclosed.\nUsers are advised to take immediate defensive measures, as the vendor has not yet addressed the reported issue.",
  "technicalDetails": "The vulnerability is situated in the 'Cookie Helper' component within 'App/Home/Model/UserModel.class.php'. The root cause stems from improper validation and handling of the 'Username' argument during the authentication or session restoration process.\nIn typical authentication workflows, the CMS likely relies on cookie data to identify and authenticate users. The implementation fails to sufficiently verify the integrity or authenticity of the 'Username' parameter provided within the cookie-based authentication mechanism.\nAn attacker can exploit this by crafting a malicious request or manipulating the cookie containing the 'Username' argument. By providing an arbitrary or specifically crafted 'Username' value, an attacker can bypass the intended authentication checks.\nThe attack flow proceeds as follows: First, the attacker intercepts or crafts an HTTP request targeting the affected application. Second, the attacker injects the manipulated 'Username' value into the cookie parameter, which the 'UserModel.class.php' component processes without adequate server-side validation against the actual session state or database. Third, the application incorrectly trusts this input, resulting in the establishment of an authenticated session for the specified username.\nThis vulnerability is classified as improper authentication because it allows an attacker to masquerade as an arbitrary user. Because this occurs remotely without requiring prior credentials, the attack surface is exposed to any network-connected entity capable of reaching the application.\nThe post-exploitation impact is severe, as it facilitates full unauthorized access to the target user's context. If the manipulated username corresponds to an administrative account, the attacker may achieve complete system compromise. The existence of public exploit code lowers the barrier for entry, allowing attackers to utilize automated tools to conduct mass exploitation efforts across exposed instances."
}