CWEweakness

CWE-1275 Sensitive Cookie with Improper SameSite Attribute

Medium Official page ↗
Abstraction
Variant
Structure
Simple
Status
Incomplete
Likelihood of exploit
Medium
Languages
Not Language-Specific
CWE version
5.0

Description

The SameSite attribute for sensitive cookies is not set, or an insecure value is used.

Common consequences

• Confidentiality, Integrity, Non-Repudiation, Access Control: Modify Application Data — If the "None" value is used, a website may create a cross-domain POST HTTP request to another website, and the browser automatically adds cookies to this request. This may enable Cross-Site-Request-Forgery (CSRF) attacks if there are no additional protections in place (such as Anti-CSRF tokens). The likelihood of the integrity breach is Low because a successful attack does not depend solely on an insecure SameSite attribute. In order to perform a CSRF attack, many other conditions might need to be met, such as the lack of CSRF tokens, no confirmations for sensitive actions on the website, a "simple" "Content-Type" header in the HTTP request, etc.

Potential mitigations

• [Implementation] Set the SameSite attribute of a sensitive cookie to "Lax" or "Strict". This instructs the browser to apply this cookie only to same-domain requests, which provides a good Defense in Depth against CSRF attacks. When the "Lax" value is in use, cookies are also sent for top-level cross-domain navigation via HTTP GET, HEAD, OPTIONS, and TRACE methods, but not for other HTTP methods that are more likely to cause side-effects of state mutation.

Detection methods

• Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Observed examples

• CVE-2022-24045: Web application for a room automation system has client-side JavaScript that sets a sensitive cookie without the SameSite security attribute, allowing the cookie to be sniffed

Related

Attack pattern · CAPEC (1)

  • CAPEC-62 Cross Site Request Forgery attack pattern

Observed example · CVE (1)

  • CVE-2022-24045 A vulnerability has been identified in Desigo DXR2 (All versions < V01.21.142.5-22), Desigo PXC3 (All versions < V01.21.142.4-18), Desigo… vulnerability

Can precede · CWE (1)

  • CWE-352 Cross-Site Request Forgery weakness

Child of · CWE (1)

  • CWE-923 Improper Restriction of Communication Channel to Intended Endpoints weakness

Referenced by CAPEC · weakness (1)

  • CAPEC-62 Cross Site Request Forgery attack pattern

Referenced by CVE · weakness (33)

  • CVE-2026-107229 The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. vulnerability
  • CVE-2026-107280 The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. vulnerability
  • CVE-2026-61687 Hatchet is a platform for orchestrating background tasks, AI agents, and durable workflows at scale. vulnerability
  • CVE-2026-53660 Open Access Management (OpenAM) is an access management solution. vulnerability
  • CVE-2026-69215 Http4s is a Scala interface for HTTP services. vulnerability
  • CVE-2026-81888 @hono/oauth-providers is Authentication middleware for Hono. vulnerability
  • CVE-2026-47889 A WebFlux application running on the Jetty 12 Core reactive adapter serializes response cookies without the sameSite attribute. vulnerability
  • CVE-2026-73847 Emlog is an open source website building system. vulnerability
  • CVE-2026-55688 The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. vulnerability
  • CVE-2026-8409 Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/dialog/logs/delete. vulnerability
  • CVE-2026-8410 Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/dialog/logs/bulk/delete. vulnerability
  • CVE-2026-8411 Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/dialog/page/bulk/delete. vulnerability
  • CVE-2026-8412 Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/dialog/page/bulk/cache. vulnerability
  • CVE-2026-8413 Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/dialog/page/bulk/design. vulnerability
  • CVE-2026-8414 Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/dialog/event/duplicate. vulnerability
  • CVE-2026-8415 Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/dialog/express/association/reorder. vulnerability
  • CVE-2026-8416 Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/backend/file addFavoriteFolder($id). vulnerability
  • CVE-2026-8427 Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/backend/file… vulnerability
  • CVE-2026-8432 Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/backend/file star(). vulnerability
  • CVE-2026-8433 Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/backend/file rescan(). vulnerability
  • CVE-2026-8434 Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/backend/file rescanMultiple(). vulnerability
  • CVE-2026-8435 Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/backend/file approveVersion(). vulnerability
  • CVE-2026-1697 The Secure and SameSite attribute are missing in the GraphicalData web services and WebClient web app of PcVue in version 12.0.0 through… vulnerability
  • CVE-2025-52628 HCL AION is affected by a Cookie with Insecure, Improper, or Missing SameSite vulnerability. vulnerability
  • CVE-2023-53957 Kimai 1.30.10 contains a SameSite cookie vulnerability that allows attackers to steal user session cookies through malicious exploitation. vulnerability
  • CVE-2025-36134 IBM Sterling B2B Integrator and IBM Sterling File Gateway 6.0.0.0 through 6.1.2.7 and 6.2.0.0 through 6.2.0.5 and 6.2.1.1 could disclose… vulnerability
  • CVE-2024-42212 HCL BigFix Compliance is affected by an improper or missing SameSite attribute. vulnerability
  • CVE-2024-30155 HCL SX does not set the secure attribute on authorization tokens or session cookies. vulnerability
  • CVE-2025-24387 A vulnerability in OTRS Application Server allows session hijacking due to missing attributes for sensitive cookie settings in HTTPS… vulnerability
  • CVE-2025-24897 Misskey is an open source, federated social media platform. vulnerability
Show all 33 ›

Referenced by OWASP · mapped cwe (2)

  • A01:2025 Broken Access Control Top 10 2025
  • A01:2021 Broken Access Control Top 10 2021