/

CVE-2026-86306

Severity:

HIGH RISK

(7.3)

Improper Authentication (CWE-287) in light0011 Cookie

CVE-2026-86306

Deferred

Vulnerability type

Category:

Improper Authentication

CWE:

CWE-287

Impact:

Unauthorized access and authentication bypass

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A remote improper-authentication weakness in the light0011 CMS Cookie Helper may allow an attacker to manipulate the Username argument and bypass intended authentication checks.

The issue is particularly risky where user-controlled cookie or authentication values are accepted without adequate verification, and public exploit information may increase attack activity.

Affected context

The weakness is associated with the Cookie Helper functionality in App/Home/Model/UserModel.class.php within the light0011 CMS. It may be present where username-related cookie values are processed remotely and authentication decisions rely on those values without sufficiently binding them to a validated session or server-side identity.

Exploit preconditions

  • Attack surface: Remotely accessible CMS authentication or cookie-handling functionality
  • Required access: The ability to send requests containing a manipulated Username argument; prior authentication may not be required
  • Trigger point: Processing of the Username value during authentication or session-related handling
  • Why exploitation is possible: Authentication logic may accept attacker-controlled identity information without adequately verifying its authenticity, integrity, or association with a valid account session

Why this happens

The underlying bug is an improper-authentication design in which an identity-bearing input can influence access decisions without sufficient server-side verification. This maps to CWE-287: Improper Authentication, where the application does not reliably establish that a requester is the legitimate user associated with the supplied identity information.

At an abstract level, the insecure pattern involves trusting a username or cookie-derived identity as an authentication factor rather than treating it as untrusted input that must be validated against protected session state and server-side account records.

Potential impact

  • An attacker may bypass authentication controls
  • Unauthorized users could access protected application functionality
  • Sensitive account or application data could be exposed
  • Attackers could perform actions under another user's identity
  • Compromised accounts could be used for further application abuse

General mitigation guidance

Mitigation generally focuses on ensuring that identity claims from cookies or request parameters do not independently establish authentication.

Common defensive patterns include:

  • Deriving authenticated identity from protected, server-side session state
  • Validating cookie integrity with authenticated protection mechanisms
  • Rejecting client-supplied identity values that are not associated with a verified session
  • Applying consistent authorization checks after authentication
  • Limiting session and application privileges according to least-privilege principles
  • Invalidating potentially exposed sessions and reviewing authentication-related logs

These controls reduce reliance on attacker-controlled input and help contain impact if an identity-bearing value is manipulated.

How teams detect issues like this

Organizations can assess for this class of issue through:

  • Static analysis rules that identify authentication decisions based directly on request parameters or cookie values
  • Code review checks for username fields used as authentication evidence
  • Tests that compare authorization behavior across modified identity-related inputs
  • Monitoring for unusual username changes, session anomalies, and access to accounts from inconsistent locations or devices
  • Policy enforcement requiring server-side session validation for authenticated identity

Automated security review tools may help identify trust-boundary violations, but authentication flows should also receive targeted manual review.

Sources

SourceLink
github.comgithub.com/light0011/cms/
github.comgithub.com/light0011/cms/issues/11
vuldb.comvuldb.com/cve/CVE-2026-86306
vuldb.comvuldb.com/submit/894817
vuldb.comvuldb.com/vuln/399479
vuldb.comvuldb.com/vuln/399479/cti

Frequently asked

questions

Yes. The reported attack path is remote and involves manipulating a Username argument processed by the Cookie Helper. The exact scope depends on deployment and authentication-flow details.

Not necessarily. The description indicates that the weakness may allow authentication to be improperly established through a manipulated identity value, although access requirements can vary by configuration.

Do not treat client-supplied usernames or cookie values as proof of identity. Use protected server-side sessions, validate integrity, and perform authorization checks against the verified session identity.

Define clear trust boundaries for authentication data, test tampering scenarios, require server-side identity verification, and monitor for anomalous authentication and session activity.

Find out what's already
exploitable in your codebase.